Connect your agent
The MCP server, tokens, and scopes.
Vortex has an MCP server over your projects' live data. It is how a coding agent answers "how is my app doing?" with numbers.
Connect
Mint a personal access token in the dashboard under Account → MCP
(tokens start vtx_mcp_, shown once). Then:
claude mcp add --transport http vortex https://<your-dashboard-host>/mcp \
--header "Authorization: Bearer <vtx_mcp_token>"
Any MCP client over streamable HTTP works the same way. OAuth 2.1 discovery is also published at the same origin for clients that prefer it.
Scopes
| Scope | Grants |
|---|---|
mcp:read | Every analysis tool. The default; all tokens have it. |
mcp:annotate | Additionally, create_annotation — the server's only write. Request it when minting the token. |
The tenant boundary comes from the token, never from tool arguments: a token can only see its own organisation's projects.
For the integration itself
The dashboard's Setup tab generates an integration guide for your agent. It covers the SDK, your event taxonomy, and has the agent verify its own wiring by reading events back over MCP before it hands the work over.
This docs site also serves /llms.txt and a full-content
/llms-full.txt, so an agent can read the documentation the same way you
are reading this page.