MCP
Natural runs a hosted Model Context Protocol server at https://mcp.natural.co. Connect OAuth-capable MCP clients such as Codex, Cursor, and Claude Code without creating or pasting an API key.
Install
Bootstrap (AI assistants, recommended)
Ask your AI assistant to read Natural’s agent playbook:
The assistant should install the MCP server, start OAuth, and tell you when to approve the Natural authorization page in your browser.
Codex
codex mcp login opens the browser OAuth flow. Natural’s MCP connector grants its tools access to payments, wallet balances and bank movement, agent reads and creation, and customer invitations.
Cursor / cursor-agent
Merge Natural into ~/.cursor/mcp.json or .cursor/mcp.json:
Then authenticate:
Use agent mcp list-tools natural to verify. If the Cursor editor does not show Natural immediately, refresh MCP tools or restart the window.
Claude Code
Then run /mcp inside Claude Code, choose natural, and select Authenticate. Claude Code opens the browser OAuth flow from there.
Any other MCP-aware host
If your host is not listed above, look for its MCP server or connector settings. Most hosts have a command, config file, or UI action for adding a remote MCP server and signing in.
Configure Natural with no Authorization header:
CLI OAuth fallback
If a host can run terminal commands but cannot do MCP OAuth, use the Natural CLI’s browser OAuth:
API-key fallback
Use an API key only when hosted MCP OAuth and CLI OAuth cannot work: headless CI, SDK or REST integrations, non-interactive scripts, or MCP hosts that support neither remote-server OAuth nor a CLI.
Claude Code fallback:
What you can do
The connector exposes 14 tools, each an intent-shaped wrapper around the Natural API. Each tool absorbs the orchestration (wallet resolution, idempotency keys, agent headers) so the agent sends a single natural-language call.