Skip to main content

​
AUVY MCP Server

The hosted AUVY MCP server lets MCP-compatible assistants use AUVY resources and preconfigured integration tools without writing client code yourself.

​
Hosted Endpoint

https://mcp.auvy.ai/mcp

​
What You Can Do

OAuth + API Key

Connect with OAuth or an Authorization: Bearer ak_live_... header.

Browse And Read

Use tools like grep, search, read, and get_session.

Invoke Workflows

Use invoke to run receptors from your assistant.

MCP Apps

Some read responses can render a receptor viewer in clients that support MCP Apps.

​
Basic Configuration

Add the hosted endpoint to your MCP client: 
{
  "mcpServers": {
    "auvy": {
      "url": "https://mcp.auvy.ai/mcp"
    }
  }
}
For direct API-key auth, include headers: 
{
  "mcpServers": {
    "auvy": {
      "url": "https://mcp.auvy.ai/mcp",
      "headers": {
        "Authorization": "Bearer ak_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

​
Setup

Prerequisites: An MCP-capable assistant (ChatGPT, Claude Desktop, Cursor) and an AUVY account. Add the hosted endpoint to your client:
  • Cursor: ~/.config/cursor/mcp.json
  • Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows)
  • ChatGPT: Settings → Integrations → MCP Servers
After adding, restart the assistant and verify tools (e.g. get_session or list receptors) are available. Troubleshooting: Connection failed → check URL https://mcp.auvy.ai/mcp and restart. Auth errors → ensure API key is valid or complete OAuth. Tools not available → confirm server in client list and auth completed.

​
Authentication

  • OAuth 2.1 — best when your MCP client supports interactive sign-in. First tool call triggers auth; complete sign-in and consent.
  • Bearer API key — always supported. Add to config: "headers": { "Authorization": "Bearer ak_live_..." }. Optional: X-Brain-Id for brain-scoped search/reads.
If you supply API-key headers, OAuth is not required. All auth uses HTTPS; tokens are managed by your client; the server only accesses resources in your AUVY account. For auth errors, verify Bearer format, complete OAuth if used, or disconnect/reconnect the server.

​
Common Tools

  • get_session
  • grep, search, read, cat
  • grep_history, read_history
  • invoke
  • connect_execute (run Connect integration tools)
  • list_receptors, list_pathways, list_neurons, list_reflexes
  • write, write_reflex, create_resource, store, edit
  • web_read, web_search
The server exposes shared AUVY tools and Connect integration tools via direct execution: you select integrations and tools, and run them with connect_execute (integration_id, tool_name, tool_config). The live server is the source of truth for the tool list. See the Tools Reference for practical usage patterns.

​
Next Steps