A manual token lets an MCP client that can’t sign in connect to AppNatively. Generate it under Manual token in the MCP Server settings, then send it with every request as Authorization: Bearer plus the token. It gives exactly the same access as signing in, lasts 90 days, and is shown only once.
When should I use a manual token?
Only when your client can’t open AppNatively’s sign-in page – for example, a client that only lets you set a URL and request headers. Claude, ChatGPT, Cursor, VS Code and Claude Code can all sign in, so they don’t need one.
How to use a manual token
1. Open the MCP Server settings
Go to Integrations and click Settings on the MCP Server card, or click MCP in the App Editor’s top bar.
2. Generate a token
Under Manual token, click Generate token. Copy it right away – it’s shown once and discarded when you close the panel.
3. Add it to your client
Use the server URL https://appnatively.com/mcp and send the token as a header:
1Authorization: Bearer YOUR_TOKENFor example, in Cursor’s mcp.json:
1{2 "mcpServers": {3 "appnatively": {4 "url": "https://appnatively.com/mcp",5 "headers": { "Authorization": "Bearer YOUR_TOKEN" }6 }7 }8}Or in Claude Code:
1claude mcp add --transport http appnatively https://appnatively.com/mcp \2 --header "Authorization: Bearer YOUR_TOKEN"Important: treat the token like a password. Don’t commit it to a code repository or share it in chat.
How long does a manual token last?
90 days. After that, generate a new one and swap it into your client. Generating a new token doesn’t cancel older ones – each stays valid until it expires or you revoke them all.
Clients using a manual token don’t appear under Connected apps; that list is only for clients that signed in.
How do I revoke manual tokens?
Click Revoke all tokens and confirm. Every client using a manual token stops working immediately. Clients that signed in, and your own browser sessions, aren’t affected.
To disconnect assistants that signed in, see Manage and disconnect AI assistants.