Jeeves MCP Server

⚠️ The Jeeves MCP server is in beta

Tools and behavior may change. We'll announce material changes in the changelog below. Questions and feedback: see Support.

Jeeves is a global banking platform for businesses. The Jeeves MCP server lets AI assistants and autonomous agents manage your company's finances — ask about card spend, pay a vendor, pull a statement, or submit a reimbursement, all without opening the Jeeves app. Whether you're chatting interactively or running an automated workflow, any MCP-compatible client can connect.

MCP (Model Context Protocol) is an open standard that lets AI assistants and agents securely access and act on data from external services — both interactively and in fully automated pipelines. The Jeeves MCP server implements this standard over HTTP.

Who this is for

The Jeeves MCP server is available to companies with an active Jeeves account. Access is scoped to your Jeeves user and role, so what your assistant can see and do matches what you can see and do in the Jeeves app.

Not a Jeeves customer yet? Talk to our team to get set up. If your company already uses Jeeves but you don't have credentials, ask your Jeeves administrator.

What you can do

Grouped by what you're trying to accomplish. The exact tool list evolves — reconnect your client to pick up new tools.

• Understand your spend — query transactions with filters, export filtered transactions to CSV, review company accounts and balances.
• Pull statements — list and download cash and credit statements, or fetch the latest credit statement directly.
• Manage cards — list and filter company cards, issue new virtual cards, update names, spending limits, and reset intervals.
• Pay vendors and handle bills — review bill pay invoices, manage vendors and their payment details, work with SAT invoices including bulk status updates (Mexico).
• Handle reimbursements — submit a reimbursement with receipts attached, check status, and configure the payout account.
• Query your organization — users, departments, approval policies, and merchant category controls.

What you can do depends on your Jeeves role. Employees see their own data; Admins and Bookkeepers see company-wide data. See Available Tools for the tool-by-tool breakdown.

MCP is built for AI assistants and agents. For bulk operations, backend integrations, webhooks, or anything the MCP tool set doesn't cover, use the Jeeves REST API instead.

Prerequisites

Before you begin:

• An active Jeeves account (visit tryjeeves.com to get started)
• A supported MCP client installed (Claude, Cursor, Codex, or any MCP-compatible tool)
• For Claude Desktop only: Node.js v20 or later

Quickstart

The Jeeves MCP server is compatible with any MCP client that supports HTTP transport. Once connected, your AI assistant or agent can take actions on your Jeeves account based on your role — viewing transactions, managing cards, paying bills, handling reimbursements, and more.

MCP Server URL

https://mcp-prod.jeev.es/mcp

The configurations below use OAuth, the default and recommended authentication method — on first connection, your client opens a browser window where you sign in to your Jeeves account. If your client can't use OAuth, or you need automated access, see API Key.

1. Claude Code

Register the server from the command line:

claude mcp add --transport http jeeves https://mcp-prod.jeev.es/mcp

To verify the connection:

claude /mcp

2. Claude Desktop

Add the server to your Claude Desktop configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "jeeves": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp-prod.jeev.es/mcp"]
    }
  }
}

Restart Claude Desktop after saving the file. Node.js v20 or later is required for mcp-remote.

3. Cursor

Open Cursor Settings → Customize → MCPs → New MCP Server. This opens your mcp.json file — add the following entry:

{
  "mcpServers": {
    "jeeves": {
      "url": "https://mcp-prod.jeev.es/mcp"
    }
  }
}

4. Codex

Register the server from the command line:

codex mcp add jeeves --url https://mcp-prod.jeev.es/mcp

To list the MCP servers:

codex mcp list

5. Claude Connectors — coming soon

A Jeeves connector is coming to the Claude Connectors directory. It exposes read tools only — for write access, install as a custom connector at https://mcp-prod.jeev.es/mcp.

Tools available in the connector

Descriptions and role access for each tool are in Available Tools.

Authentication

The server supports two authentication methods: OAuth (recommended) and API keys.

OAuth (Recommended)

OAuth is supported by Claude Code, Claude Desktop, Cursor, and Codex. On first connection, your client will open a browser window where you sign in to your Jeeves account and approve access. No manual token management is required — your client handles session refresh automatically.

OAuth scopes

OAuth tokens carry one or both of two scopes:

Each tool's type is shown in the Type column of Available Tools. A call to a tool without the required scope is rejected with HTTP 403 and an insufficient_scope error — your role alone is not enough for write actions over OAuth.

There is currently no option to request a reduced, read-only connection — standard connections are granted both scopes, and access is governed by your Jeeves role.

API key connections are not scope-restricted: an API key grants the full tool surface permitted by your Jeeves role, including write tools. This is why the security notice below matters.

API Key

Use API key authentication when your client does not support OAuth, or when you need programmatic or automated access.

To generate an API key:

1. Sign in to the Jeeves web application.
2. Navigate to Settings → MCP and click Create MCP Credential.
3. Copy the key immediately — it is shown only once. Store it in a password manager or secrets vault.

Security notice: Your API key grants full access to your Jeeves account, including the ability to initiate payments and manage cards. API keys are not scope-restricted — every tool your role permits, read or write, is available to whoever holds the key. Never share it, commit it to source code, or include it in client-side applications. If a key is compromised, revoke it immediately from Settings → MCP.

Include the key in the x-api-key header on every request:

x-api-key: YOUR_API_KEY

1. Claude Code

claude mcp add --transport http jeeves https://mcp-prod.jeev.es/mcp \
  --header "x-api-key: YOUR_API_KEY"

2. Claude Desktop

{
  "mcpServers": {
    "jeeves": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp-prod.jeev.es/mcp",
        "--header",
        "x-api-key: YOUR_API_KEY"
      ]
    }
  }
}

3. Cursor

{
  "mcpServers": {
    "jeeves": {
      "url": "https://mcp-prod.jeev.es/mcp",
      "headers": {
        "x-api-key": "YOUR_API_KEY"
      }
    }
  }
}

4. Codex

Codex reads the API key from an environment variable and sends it as a bearer token. Export your key first, then register the server:

export JEEVES_API_KEY="YOUR_API_KEY"

codex mcp add jeeves --url https://mcp-prod.jeev.es/mcp \
  --bearer-token-env-var JEEVES_API_KEY

codex mcp list

Verify your connection

Once your client is configured, confirm it's working by asking your assistant:

• "What Jeeves cards do I have?"
• "Show me our Jeeves transactions from last month"
• "List my Jeeves accounts and balances"

In Claude Code, run /mcp and confirm jeeves appears in the connected servers list with its tools listed. In Claude Desktop, open Settings → Connectors and confirm jeeves shows as connected. In Cursor, open Settings → Customize → MCPs and confirm jeeves shows a green status. In Codex, run codex mcp list.

The tools you see depend on your Jeeves role — see Available Tools. If you expected a tool and don't see it, your role may not have access to it.

Available Tools

The tables below list all tools exposed by the server, grouped by functional area.

About roles: Jeeves has four roles — Admin, Manager, Employee, and Bookkeeper. Your role is assigned by your company's Jeeves administrator. The Access column shows which roles can use each tool. Tools outside your role are hidden from your assistant or agent and will not appear.

About types: Read tools only retrieve data. Write tools change state in your Jeeves account — see Agent safety and write actions. Over OAuth, write tools additionally require the mcp:tools:write scope.

Accounts and Transactions

Statements

Cards

Payments and Bill Pay

Reimbursements

Vendors

Organization

Files

Agent safety and write actions

Some tools change state in your Jeeves account — they're marked Write in Available Tools. When you connect an AI assistant or an autonomous agent, those tools become available to it within the limits of your role.

Role enforcement: tool access is enforced server-side. Tools outside your role are hidden from your assistant and rejected if called — an agent cannot use a tool your role doesn't permit.

OAuth scopes: over OAuth, write tools additionally require the mcp:tools:write scope — see OAuth scopes.

Retries: write calls are not deduplicated. If a write call fails or times out, check the result in the Jeeves app before retrying — re-running the same call may create a duplicate.

Recommendations for autonomous workflows: use a role scoped to the minimum needed, keep write-capable credentials out of shared environments, and rotate API keys regularly.

Testing safely

There's no separate sandbox environment for the Jeeves MCP server — it connects to your live Jeeves account. When you're first evaluating it, we recommend:

• There is currently no read-only credential option — a connection has access to every tool your role permits, read and write. A limited role reduces write access but does not remove it: every role, including Employee, can submit reimbursements and upload files.
• Explore with read tools first — list_transactions, list_cards, list_accounts — before enabling anything that writes.
• If you're testing card creation, issue virtual cards with a low spending limit and delete them when you're done.
• Use a separate API key for testing so you can revoke it independently.

Permissions

Anyone with a Jeeves account can connect using their own credentials — no extra setup needed. Your assistant or agent gets the same access you have in the Jeeves app, based on your Jeeves role and the features enabled for your company.

This keeps things simple and safe: the tool list you see is automatically tailored to you, and everything your assistant does stays within your existing permissions.

Troubleshooting

The OAuth window opens but the connection never completes

• Claude Code: run /mcp, select jeeves, and choose "Clear authentication", then reconnect.
• Claude Desktop / Cursor: remove the server from your config, restart the app, then re-add it.
• Clear cached MCP auth: rm -rf ~/.mcp-auth
• Confirm you're signed in to the correct Jeeves account in your browser before starting the flow.

401 Unauthorized

Your API key is invalid or has been revoked. Generate a new one in Settings → MCP. Note that keys are shown only once at creation.

403 Forbidden on a specific tool

Either your Jeeves role doesn't have access to that tool — see the Access column in Available Tools and contact your Jeeves administrator to change your role — or, on an OAuth connection, your token lacks the mcp:tools:write scope required for write tools (the error will say insufficient_scope).

Some tools are missing, or newly released tools don't appear

Tools are filtered by your role, so you'll only see what your role permits. If you're expecting a newly released tool, disconnect and reconnect the server in your client to refresh the tool list.

Claude Desktop shows the server as failed to start

mcp-remote requires Node.js v20 or later. Check with node --version. If you're below v20, upgrade Node and restart Claude Desktop.

A query returns more results than the assistant can handle

Ask the assistant to narrow the request — add a date range, account, or status filter.

Still stuck? See Support.

Support

• Setup and usage questions: Jeeves Help Center
• Bugs and feedback on the MCP server: Jeeves Help Center
• Role or access changes: contact your Jeeves administrator.

We read all MCP feedback — if a tool is missing or a workflow doesn't work the way you'd expect, tell us.

Changelog

We'll record material changes to the tool surface and server behavior here.

Resources

• Model Context Protocol specification
• Jeeves Help Center
• Jeeves API Documentation