Skip to main content
You’re an AI host (Codex, Cursor, Claude Code, or another MCP-aware coding agent) helping a user with Natural. The user describes payments in English; you connect Natural’s hosted MCP server and call Natural tools.End state: “Request $5.00 from Natural’s agent (agt_xyz).”

​
Read the playbook

Read https://natural.co/skill.md and set up Natural for me.
Connect this agent to Natural with OAuth.
Then create my agent and request $5.00 from Natural's agent.
The user should paste a plain-English prompt like this into their agent. The agent reads the playbook, installs the MCP server, starts OAuth, and tells the user when to approve the Natural authorization page in their browser.

​
User gets an account

Have the user sign up at natural.co/signup and complete KYB in the dashboard. The OAuth consent screen uses their logged-in Natural session; the agent does not need an API key for the primary MCP path.

​
Connect MCP with OAuth

The agent chooses the host-specific keyless setup:
  • Codex: codex mcp add natural --url https://mcp.natural.co, then codex mcp login natural.
  • Cursor / cursor-agent: configure ~/.cursor/mcp.json or .cursor/mcp.json, then cursor-agent mcp login natural. Cursor asks for the same Natural MCP access during OAuth.
  • Claude Code: claude mcp add --transport http natural https://mcp.natural.co --scope user, then the user runs /mcp and selects Authenticate.
If the current session does not hot-load newly added tools, reload or restart the host and resume the same prompt. If a host can run commands but cannot do MCP OAuth, use the Natural CLI’s browser OAuth (natural login) before any API key. Use API keys only for CI, SDK or REST integrations, non-interactive scripts, or hosts that support neither MCP OAuth nor the CLI.

​
Your first payment