Use an agent key for advanced setups
Most people should connect in the browser. If you are setting up a script, automation, or command-line tool that cannot open a sign-in window, create an agent key instead.
Last updated
Most people should connect in the browser. If you are setting up a script, automation, or command-line tool that cannot open a sign-in window, create an agent key instead.
Creating one
- Go to Account → AI Agents.
- Under Personal keys, click to create one.
- Give it a name you will recognise later, pick an access level, and set a daily spending cap if the level allows spending.
- Copy the key.
The key is shown once, at creation. Mintfunnel does not store a recoverable copy. If you lose it, revoke it and mint another.
Using one
Send it as a bearer token on requests to the MCP endpoint:
Authorization: Bearer <your key>
The endpoint is the same as for browser connections:
https://app.mintfunnel.co/mcp
What is different from a browser connection
Personal keys are a convenience for a narrow case, and they trade away some safety to get there:
- They last 365 days, against 60 minutes for an access token from the browser flow.
- They are a static string. Anyone holding it can use it until it is revoked.
- There is no consent screen at the point of use, so the level and cap you set at creation are the only limits.
Everything else still applies. The key carries an access level and a daily spending cap, every write still requires a preview and a confirmation, every call is logged, and cross-account access is impossible.
Keeping them safe
- Treat a key like a password. Store it in a secret manager, not in a repository, a shared document, or a chat message.
- Give each tool its own key, so one can be revoked without disrupting the others.
- Use the lowest level that works. Most automation only needs Read.
- Revoke keys you are not actively using. Account → AI Agents shows each key's name and when it was last used, which makes the unused ones easy to spot.
Revoking
From Account → AI Agents, revoke any key individually. It stops working on the next request. Revoking a key does not affect your browser-based connections.
