Attrove MCP Integration — Model Context Protocol

Per-user scoping

Each MCP session is scoped to a single Attrove user. The AI assistant can only access data belonging to the configured user. It sees exactly what that user's authenticated Attrove account grants access to. This makes MCP ideal for development testing and for letting end users connect their own AI tools.

Recommended Setup

The best path is the CLI hosted install. Hosted remote MCP is the default; it writes a remote MCP config pointed at Attrove, lets the client discover OAuth automatically, and avoids pasting secrets into client JSON by hand.

# Pick your client
npx @attrove/cli install codex
npx @attrove/cli install claude-code
npx @attrove/cli install cursor
npx @attrove/cli install claude-desktop

Claude Code defaults to project scope in .mcp.json. Cursor, Claude Desktop, and Codex default to user scope. Codex uses ~/.codex/config.toml. After install, open your client and finish OAuth when prompted.

Codex

Codex connects to hosted streamable HTTP MCP servers from its config.toml file. The CLI writes the canonical Attrove server entry; then Codex completes hosted OAuth with its own login command.

npx @attrove/cli install codex
codex mcp login attrove

Verify the first useful answer

A green install only proves the MCP server is reachable. First list connected sources, then ask for an answer that cites the messages, meetings, or events it used. Prompts: "Use Attrove to list my connected integrations." Then: "What needs my attention this week? Include the source messages or meetings you used."

Hosted Endpoint

Attrove hosts an HTTP MCP endpoint that supports both sk_ token and OAuth authentication. Clients can connect directly without running a local server.

// Hosted MCP endpoint
https://api.attrove.com/mcp

// Supports two auth modes:
// 1. sk_ token: Authorization: Bearer sk_live_...
//    + X-Attrove-User-Id: <user-uuid>
//
// 2. OAuth (Supabase JWT): Authorization: Bearer eyJ...
//    User accesses their own data (no user ID header needed)

With OAuth, your users authenticate as themselves and access their own connected data. No server-side token management is needed on your end for the hosted path.

Advanced Local Fallback

If you need to run the stdio server locally or intentionally want credential-backed local MCP, use the advanced fallback path.

npx @attrove/cli login
npx @attrove/cli local install claude-code
npx @attrove/cli connect gmail

Manual MCP config (fallback — prefer npx @attrove/cli install <client>):

{
  "mcpServers": {
    "attrove": {
      "command": "npx",
      "args": ["-y", "@attrove/mcp@latest"],
      "env": {
        "ATTROVE_SECRET_KEY": "sk_live_...",
        "ATTROVE_USER_ID": "a1b2c3d4-e5f6-..."
      }
    }
  }
}

Available Tools

Tools are scoped to the authenticated user's data. Listing, search, query, integrations, events, meetings, notes, and goal status reads are read-only. attrove_push_note and attrove_push_meeting write into that same user's context; delete tools reversibly archive pushed meetings and notes; the goal tools can create goals, queue evaluations, attach goal notes, confirm status, and poll goal events. Goal status changes always require a reason.

• attrove_query — ask natural language questions and get AI-generated answers with source references.
• attrove_search — semantic search across email, chat, calendar, and meetings. Filter by date range or sender domain.
• attrove_integrations — list connected integrations and their sync status.
• attrove_events — list calendar events with attendees, locations, and meeting links.
• attrove_meetings — list meetings with AI-generated summaries, action items, and attendees.
• attrove_notes — list saved notes, decisions, and observations already attached to the authenticated user context.
• attrove_push_note — write a note into the authenticated user context so future agents can reuse decisions, observations, or session state.
• attrove_push_meeting — save a meeting transcript or summary from another meeting MCP, a transcript export, or manual notes.
• attrove_delete_meeting — reversibly archive a pushed meeting so it is hidden from meeting, search, and query results.
• attrove_delete_note — reversibly archive a note so it is hidden from notes, search, and query results.
• attrove_create_goal — create a watched outcome. Attrove keeps re-evaluating it against the communication stream and updates health with cited evidence.
• attrove_list_goals — list goals, optionally filtered by lifecycle or health. The fastest way to find outcomes that need attention.
• attrove_get_goal_status — full goal record with the latest snapshot: summary, risk signals, next actions, and the evidence refs behind the state.
• attrove_evaluate_goal — queue a fresh evaluator run for a goal. Async; rate-limited to 6 manual runs per goal per hour.
• attrove_add_goal_note — attach a manual note as goal evidence. Indexed within seconds and citable by future evaluator runs.
• attrove_confirm_goal_status — human confirm or override of a goal lifecycle or health, with a required reason. The only path for completing, archiving, or cancelling a goal.
• attrove_goal_events — poll goal lifecycle transitions as an append-only feed with cursor metadata.

Ready to embed Attrove for your users?

Get your API credentials and start building the integration for your product: sign up free.

• Quickstart Guide — create users & connect data
• API Reference — all endpoints & examples