movere Docs

Connect your AI agent

Audience: anyone using an MCP-capable agent or editor (Cursor, Claude Code, VS Code, and others) who wants Mooov docs and API schemas available to it while building an integration.

Mooov runs an MCP server at https://mcp.mooov.money/mcp (MCP Streamable HTTP). Point your agent at it, sign in through the Mooov consent screen, and it can search these docs, list the gateway API operations, retrieve request / response / webhook schemas, and (with the scopes you grant) act on your own account data.

1. What it exposes

Connect with an OAuth access token, or an access token obtained by exchanging a portal install token. Without a bearer credential, POST /mcp returns 401 with a WWW-Authenticate challenge that points at Mooov's protected-resource metadata, the same pattern Stripe's MCP uses. After you authorize, the agent receives the Tier 0 docs and schema tools plus any account-scoped tools that match the scopes you picked. Money movement stays off unless you explicitly enable it.

2. Install in Cursor

Add the Mooov MCP server to Cursor

The button opens Cursor on the machine it is clicked on; if nothing happens, Cursor is not installed there. Manual fallback: Cursor Settings -> Tools & Integrations -> Add Custom MCP, with the URL https://mcp.mooov.money/mcp.

3. Install in Claude Code

claude mcp add --transport http mooov https://mcp.mooov.money/mcp

4. Any other MCP client

Any client that speaks MCP Streamable HTTP works. The generic config:

{ "mcpServers": { "mooov": { "url": "https://mcp.mooov.money/mcp" } } }

5. Tools

Tool What it answers
mooov.search_docs Keyword search across these published docs. Returns matching pages ranked by match frequency, with a snippet around the first hit.
mooov.lookup_skill Reserved. Returns an empty list on the public server.
mooov.list_endpoints The gateway API operations from the OpenAPI spec. Filterable by tag, method, or path prefix.
mooov.describe_endpoint The full request and response schema for one operation, selected by operation_id or method + path.
mooov.list_event_types The webhook event catalog: type, summary, since-version.
mooov.describe_event Payload shape plus an example payload for one event type.

Search results and schemas reflect the MCP server's published knowledge snapshot, which is updated separately from this website. Check the linked guides for current environment restrictions and feature availability; a schema entry does not mean a capability is enabled for your account.

6. Connect your account (account-scoped tools)

To let an agent see your own payments, customers, payouts, and (when you opt in) move money, you authorize it against your Mooov account. There are two ways, both of which produce a revocable, scope-limited grant. The agent never sees your password or API keys.

Option A: OAuth (recommended)

Editors that support OAuth for MCP (e.g. Cursor) discover Mooov's authorization server automatically. When you add the account-scoped server and trigger sign-in, your browser opens the Mooov-branded consent screen. There you:

  1. see exactly which agent is asking and what it wants,
  2. pick the permissions to grant (read / write per area), with money movement off by default, and
  3. click Authorize.

The flow is standard OAuth 2.1 with PKCE: the editor registers itself dynamically, you consent in the Mooov portal, and the editor receives an access token plus a rotating refresh token. No secret is ever copied by hand. The protected-resource and authorization-server metadata are published at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.

Option B: manual install token

Prefer OAuth when your editor supports it. For a manual setup, open Developers -> Agent access in the Mooov portal, choose permissions, and click Authorize to mint a single-use install token. It is shown once. Exchange it explicitly before configuring the editor:

POST https://mcp.mooov.money/mcp/install/exchange
Content-Type: application/json

{"token":"<INSTALL_TOKEN>"}

A successful response contains access_token, grant_id, scopes and money_out. Configure the returned access_token as the bearer credential:

{
  "mcpServers": {
    "mooov": {
      "url": "https://mcp.mooov.money/mcp",
      "headers": { "Authorization": "Bearer <ACCESS_TOKEN>" }
    }
  }
}

The install token is not the MCP bearer credential. Pasting it directly into an editor's Authorization header does not perform this exchange. Store the returned access token securely. If the exchange endpoint is unavailable for your setup, use OAuth or contact support.

Managing access

Every grant is listed under Developers -> Agent access with its agent name, scopes, and money-movement flag. Revoke any grant there at any time and the agent's access stops immediately.

7. What it can't do

Without a grant: no account data, no payments, no secrets. Even with a grant, an agent can only do what you authorized, money movement (refunds, voids, instant payouts) requires the explicit money-movement permission, and credential or team-management actions are never reachable by an agent. For a full integration you still use the API itself: start with the merchant quickstart or, for platforms, the Connect protocol, and test against the sandbox.