Skip to main content

​
Configuration

Tokencraft hosts a remote MCP server with OAuth authentication. No API key or local installation required.

​
Server URL

​
Cursor

  1. Open Cursor Settings → MCP
  2. Add a new remote MCP server
  3. Set the URL to https://app.tokencraft.dev/api/mcp
  4. On first use, your browser opens for OAuth consent
  5. Approve the requested scopes

​
Claude (remote MCP)

Add the hosted URL in your client’s remote MCP configuration. OAuth endpoints are discovered automatically via:
  • /.well-known/oauth-authorization-server
  • /.well-known/oauth-protected-resource
See MCP OAuth for the full authorization flow, scopes, and token lifecycle.
OAuth tokens appear in API Settings as MCP OAuth — {client name}. You can revoke them at any time.

​
Verify setup

Ask your MCP client:
If OAuth succeeded, the client returns your workspaces.

​
Troubleshooting

​
Authentication failed

Solutions:
  1. Revoke the existing MCP OAuth — … token in API Settings and reconnect
  2. Ensure you approved all required scopes on the consent screen
  3. Check that your plan includes MCP access

​
Client doesn’t discover OAuth

Solutions:
  1. Verify the URL is exactly https://app.tokencraft.dev/api/mcp
  2. Ensure your MCP client supports remote HTTP servers with OAuth discovery
  3. Check MCP OAuth for endpoint details

​
403 on write operations

Write tools (create, update, delete, bulk import) require write:tokens scope and a workspace where your role allows API writes.

​
Other MCP clients

Any MCP client that supports Streamable HTTP and OAuth can connect to https://app.tokencraft.dev/api/mcp. The client should handle token refresh by re-running the OAuth flow when the 30-day access token expires.

​
Next Steps

MCP OAuth

OAuth flow and token lifecycle

Tools

Available MCP tools

Bulk import

Import tokensets at scale

Examples

Example interactions