Skip to main content
Cursor supports MCP servers via a project-level or global config file.

​
Global (all projects)

Edit ~/.cursor/mcp.json (create it if it doesn’t exist):

​
Project-only

Create .cursor/mcp.json in your repo root with the same contents. This is useful if different projects/agents should use different XentFi API keys — commit a .cursor/mcp.json.example with placeholders and keep the real file (with your key) out of version control.

​
Enabling it

1

Open MCP settings

Cursor Settings → MCP.
2

Confirm it's active

You should see xentfi listed with a green/active dot and its tool count.
3

Use it

In the Agent/Composer chat, XentFi tools are available automatically — Cursor’s agent will call them when relevant, or ask directly: “Use xentfi to show my agent’s wallet balances.”
Cursor spawns one subprocess per config entry and keeps it running for the session — no need to restart Cursor after the first load, only after editing mcp.json.
For a key that Cursor’s agent can use to read wallet/policy data but never move funds unattended, restrict the Policy attached to that agent’s API key in the XentFi dashboard rather than relying on client-side restrictions — xentfi_create_payment is still callable by any client holding a valid key.

​
Next steps

Tools Reference

See every available tool.

VS Code

Another local-client option.