Skip to main content
Natural runs a hosted Model Context Protocol server at https://mcp.natural.com. OAuth-capable hosts such as Claude, Claude Code, ChatGPT, Codex, and Cursor connect with browser OAuth. No API key to create or paste.
Use MCP when an AI host (Claude, Cursor, etc.) runs the agent for you. Building your own agent runtime? Use the SDKs or CLI instead.

Connect your host

Sign up and complete onboarding first; OAuth signs the host into your Natural account. Pick your tool:
Custom connectors require a paid Claude plan (Pro, Max, Team, or Enterprise). The setup is the same for claude.ai and the Claude Desktop app.
  1. In claude.ai or the Claude Desktop app, open the sidebar, select Customize, and go to the Connectors tab.
  2. Select Add custom connector and fill in the fields: name Natural, remote MCP server URL https://mcp.natural.com.
  3. Select Add, then Connect. Your browser opens Natural’s authorization page; approve it, and you are redirected back to Claude.
  4. Try it in chat:
Custom plugins require a paid ChatGPT plan (Plus, Pro, Business, or Enterprise).
  1. Open Settings → Security and turn on Developer mode.
  2. Select Plugins in the sidebar, then the + button, and fill in the fields: name Natural, MCP server URL https://mcp.natural.com, authentication OAuth.
  3. Accept ChatGPT’s unverified-server disclaimer and select Create, then Sign in with Natural. Approve Natural’s authorization page when it opens.
  4. Try it in chat:

Any other MCP-aware host

Most hosts have a UI action, command, or config file for adding a remote MCP server and signing in. Point it at https://mcp.natural.com with no Authorization header so it uses OAuth. For hosts that take mcpServers JSON:
  • Use https://mcp.natural.com; use https://mcp.natural.com/mcp only for legacy clients that require an explicit endpoint path.
  • Set the auth mode to OAuth if the host has one; a bare URL entry defaults to no auth on many hosts and silently skips sign-in.
  • After signing in, verify by listing Natural tools or calling a read-only tool like get_account_balance. If tools are missing, reload the host once and check again.

CLI OAuth fallback

If a host can run terminal commands but has no MCP OAuth flow, sign in with the Natural CLI before reaching for an API key:
natural login authenticates locally with OAuth, then the CLI’s full command surface is available.

API-key fallback

Use a key only when neither hosted MCP OAuth nor CLI OAuth works: headless CI, SDK/REST integrations, or non-interactive scripts. Pass it as the bearer token:
  • API key (sk_ntl_…) — Tool calls act as your party.
  • Agent key (ak_ntl_…) — Tool calls act as the bound agent, verified by the credential.
Keep keys out of chat, source control, and committed config.

User-scoped vs agent-scoped OAuth

Natural’s consent screen determines who the connection acts as:
  • As an agent (agent-scoped) — The default: pick one of your existing agents or create a new one during approval. Every tool call then acts as that agent with a verified binding, and audit records both the agent and the authorizing user. Agent-scoped connections can’t call create_agent or manage keys.
  • As me (user-scoped) — Tool calls are your own user/party actions, with no agent attribution needed. A consent screen with no agent selection grants user-scoped access.
To switch modes, disconnect Natural in the host and reconnect with the other selection.

What you can do

The connector exposes 24 tools, each shaped around an intent. Each one handles the orchestration for you (finding the right wallet, detecting the payer type, auto-selecting a single account), so the agent just says what it wants instead of chaining calls.

Amounts and currencies

MCP payment tools use a decimal amount and a three-letter currency code:
Natural preserves the amount you give it: $5 becomes "5.00" and $5.3 becomes "5.30" without changing the value. If an amount cannot be represented exactly (for example, a USD amount with fractions of a cent), the agent should ask which exact amount to send instead of rounding it. The payment tool accepts only exact decimal amounts without currency symbols or commas, and currency is always required. In manual approval mode, your host shows the amount, currency, and destination before the payment runs. When paying a payment request, Natural checks its current amount and currency again and stops if either changed.
This format applies to MCP. Natural’s REST API and SDKs use integer minor units. See Data formats.

Attribution for production agents

With an agent-scoped OAuth grant or an agent key, agent identity is carried by the credential. For money-moving tools, pass instanceId every run so each is auditable. With a user-scoped grant or a party API key, tool calls are user/party actions and need no attribution fields. Older integrations can still pass agentId for claimed attribution; prefer agent-scoped OAuth or agent keys for new agent integrations.

Troubleshooting

  • Missing tools after connecting — Reload the host’s MCP tools or restart the host window after OAuth completes.
  • Auth fails after a previous success — Disconnect Natural in the host, reconnect, and approve the OAuth screen again.
  • Tool reports missing account setup — Finish KYC/KYB, wallet, or linked-bank setup in the Natural dashboard, then reconnect.
For support, include the host name, server URL used, approximate timestamp, your Natural email, any request ID, any visible identifier (txn_*, prq_*, pay_*), and the exact error text.
  • Authentication — API keys and scopes
  • Agents — The autonomous-actor model behind the connector
  • SDKs — Python and TypeScript client libraries
  • CLI — For terminal and CI use