Crossmint MCP Server Tools

The Crossmint MCP server exposes the following tools. Your AI assistant chooses which tool to call based on your request. To connect a client, see Connect the Crossmint MCP Server. A connection is signed in to one environment (production or staging) and one organization. Every tool runs in that environment and organization.

Session

Tool	Description	Parameters
`whoami`	Returns the signed-in email, the environment, and the active organization.	None
`env_select`	Returns a link to open in a browser to move the connection to another environment. In the browser, you sign in to that environment and choose an organization.	`environment`: `production` or `staging`

Organizations

Tool	Description	Parameters
`orgs_list`	Lists the organizations you belong to and the ID of the active one.	None
`orgs_current`	Returns the active organization.	None
`orgs_select`	Switches the connection to another organization. For an organization that requires MFA or SSO, returns a link to open in a browser instead.	`organizationId`: as listed by `orgs_list`

Projects

The server does not keep a selected project. projects_details, the auth provider tools and every API key tool take the projectId of the project to work on, as returned by projects_list or projects_create. Project IDs belong to one organization and environment: after a switch, list the projects again.

Tool	Description	Parameters
`projects_list`	Lists the projects in the active organization.	None
`projects_details`	Returns the details of a project.	`projectId`
`projects_create`	Creates a Smart Wallets project in the active organization and returns its ID.	`name`
`projects_auth_provider_get`	Returns the auth provider (JWT authentication) of a project: the provider, JWKS URI, issuer, user ID claim and audience, and the client keys that require JWT auth.	`projectId`
`projects_auth_provider_set`	Sets the auth provider of a project.	`projectId`, `provider`, `providerId`, `jwksUri`, `issuer`, `userIdClaim`, `audience`, `confirm`

`projects_auth_provider_set` Parameters

Parameter	Description
`projectId`	The project to configure.
`provider`	`crossmint`, `auth0`, `stytch`, `firebase`, `supabase`, `kinde`, or `custom`. `crossmint` is the default. Use it to undo a change.
`providerId`	Third-party providers only: the Auth0 domain, Stytch project ID, Firebase project ID, Supabase project reference, or Kinde subdomain.
`jwksUri`	`custom` only: the https URL of the JWKS endpoint.
`issuer`	`custom` only (optional): the expected `iss` claim. If you leave it out, any issuer is accepted.
`userIdClaim`	Optional: the claim that holds the user ID. The default is `sub`.
`audience`	Optional: the expected `aud` claim. An empty string removes it. If you leave it out, the audience is kept while the issuer stays the same, and removed when you change the provider or issuer. Not accepted with `crossmint`.
`confirm`	Must be `true` when client keys of the project require JWT auth. After the change, these keys accept only JWTs from the new provider.

API Keys

Tool	Description	Parameters
`keys_list`	Lists the API keys of a project. Production server key secrets are masked.	`projectId`, `type` (optional): `server` or `client`
`keys_create`	Creates an API key in a project. A production server key secret is only returned in this response.	`projectId`, `usageOrigin`, `scopes`, `clientType`, `whitelistedOrigins`, `whitelistedAppIdentifiers`, `requiresJwtAuth`
`keys_edit`	Replaces the scopes of an API key. For a client key, also sets whether it requires JWT auth.	`projectId`, `keyId`, `scopes`, `requiresJwtAuth` (optional)
`keys_delete`	Deletes an API key. The deletion cannot be undone.	`projectId`, `keyId`, `confirm`: must be `true`

`keys_create` Parameters

Parameter	Description
`projectId`	The project to create the key in.
`usageOrigin`	`server` for a key used from a backend, or `client` for a key used from an app.
`scopes`	The API key scopes, for example `wallets.read`. The server rejects scopes the key cannot have and returns the allowed list.
`clientType`	Client keys only: `web`, `mobile`, or `desktop`.
`whitelistedOrigins`	Web client keys only: the allowed origins, for example `https://www.yourdomain.com`.
`whitelistedAppIdentifiers`	Mobile client keys only: the iOS bundle IDs or Android package names allowed to use the key.
`requiresJwtAuth`	Client keys only (optional): if `true`, every request must also include a JWT that the project’s auth provider accepts. Set the provider with `projects_auth_provider_set`. The default is `false`.

keys_edit replaces the full list of scopes. To add a scope, pass the existing scopes and the new one. If you leave out requiresJwtAuth, the key keeps its current setting.

Connect the MCP Server

Add the Crossmint MCP server to your AI client

API Keys

Scopes available to server and client keys

Introduction

Solution Guides

CLI

MCP Server

Crossmint MCP Server Tools

Session

Organizations

Projects

`projects_auth_provider_set` Parameters

API Keys

`keys_create` Parameters

See Also

Connect the MCP Server

API Keys

​Session

​Organizations

​Projects

​projects_auth_provider_set Parameters

​API Keys

​keys_create Parameters

​See Also

Connect the MCP Server

API Keys

Session

Organizations

Projects

`projects_auth_provider_set` Parameters

API Keys

`keys_create` Parameters

See Also