Tools

The MCP exposes tools your coding agents can call after the server is connected and authenticated. Tool calls run in the context of the account that authenticated the MCP server. By default, they use your primary &tag and the identity context stored in your & memory.

Thanks for your feedback!

Prerequisites

The `&` mobile app is load-bearing

Two things on this page require the & app on your phone:

Authentication. The MCP OAuth flow ends with a QR code on and.com that the & app scans and approves. The browser has no separate sign-in form. See How authentication works.
Confirming pending identity signals. Tools that write to your identity (identity_write, questions_answer) land their writes at status='pending'. They become part of your visible identity only after you approve them in the app's review queue. There is no MCP tool to approve signals.

Install the app and sign in with the same &tag before setting up the MCP.

Tool Reference

Tool	Category	What it does	Scope	Mutates data?
`ask_question`	Identity synthesis	Answers a natural-language question from the caller's identity and optional participants.	`signals:ask`	No
`find_andees`	Discovery	Finds a non-connected andee by name plus public-info constraints.	`signals:ask`	No
`identity_write`	Identity write	Saves a durable fact to the authenticated andee's `&` memory.	`signals:write`	Yes
`connections_read`	Connections	Lists the authenticated andee's active connections.	`connections:read`	No
`connections_pending`	Connections	Lists incoming and outgoing pending connection requests.	`connections:read`	No
`connections_request`	Connections	Sends a connection request to another andee by `&tag`.	`connections:write`	Yes
`connections_accept`	Connections	Accepts a pending incoming connection request.	`connections:write`	Yes
`connections_deny`	Connections	Declines a pending incoming connection request.	`connections:write`	Yes
`connections_remove`	Connections	Removes an active connection.	`connections:write`	Yes
`ask_andee`	Peer questions	Sends a free-form question to a connected andee.	`connections:write`	Yes
`questions_pending`	Peer questions	Lists open peer questions other andees asked the caller.	`connections:read`	No
`questions_list`	Peer questions	Lists peer questions the caller has sent and their lifecycle state.	`connections:read` or `connections:write`	No
`questions_answer`	Peer questions	Answers a pending peer question and writes the answer as an identity signal.	`connections:write`, `signals:write`	Yes
`questions_reject`	Peer questions	Silently declines a pending peer question.	`connections:write`	Yes
`questions_withdraw`	Peer questions	Retracts a pending peer question the caller sent.	`connections:write`	Yes

Identity Tools

Use ask_question for read-style personalization. It returns synthesized answers rather than raw signal rows. Use identity_write only for durable identity context the andee wants remembered.

Thanks for your feedback!

Discovery Tools

Use find_andees when the user mentions a non-connection and you need to resolve their &tag from public information before asking about them or sending a connection request.

Thanks for your feedback!

Connection Tools

Connection tools let agents inspect the caller's active and pending connection graph, send requests, accept or deny incoming requests, and remove active connections. They never expose identity signal content by themselves.

Thanks for your feedback!

Peer-Question Tools

Peer-question tools let agents ask connected andees questions, inspect outgoing or incoming question state, answer questions, decline questions, and withdraw pending questions. Answers become identity signals and require app review before they become visible identity context.

Thanks for your feedback!

Tools Not Exposed

identity_read is deprecated

identity_read is no longer registered on the MCP. It was replaced by ask_question, which returns synthesized answers rather than raw signal rows. The signals:read scope is also no longer advertised on the MCP well-known endpoint; existing clients that still request it are rewritten to signals:ask during consent.

andee_read is intentionally gated

andee_read is not exposed through the MCP. It remains gated pending the ENG-783 privacy and product decision about whether LLM clients should read connection-only andee profiles.

Notes

Tool availability can expand over time.

Thanks for your feedback!

Your client may show tool schemas and argument hints directly in the MCP UI.

Thanks for your feedback!

If a tool call fails because authentication is missing, expired, or missing the required scope, re-authenticate the and MCP server from your client.

Thanks for your feedback!

On this page