Server URL:
https://app.fanaura.com/mcp
Transport: Streamable HTTP
Sign-in: OAuth 2.1 with PKCE and dynamic client registration. Desktop apps may use a loopback redirect. No API key, no client ID to paste.Add the server
- Cursor
- VS Code
- Claude Code
- Gemini CLI
- Windsurf
- Codex
Add this to Open Cursor Settings, then MCP. Fanaura shows Needs login. Click it, sign in on the Fanaura page, and tap Allow access. Cursor returns you to the editor on its own.
.cursor/mcp.json in your project, or to ~/.cursor/mcp.json for every project..cursor/mcp.json
Client settings formats change often. If a field name above stops working, check your client’s MCP documentation. The URL never changes.
Any other MCP client
Any client that supports remote MCP servers over Streamable HTTP with OAuth can connect. The client needs to do four things, and most do them for you:1
Discover the sign-in server
Call
https://app.fanaura.com/mcp without a token. Fanaura answers 401 with WWW-Authenticate: Bearer realm="fanaura-mcp". The client then reads https://app.fanaura.com/.well-known/oauth-protected-resource and https://app.fanaura.com/.well-known/oauth-authorization-server.2
Register itself
POST https://app.fanaura.com/api/oauth/mcp/register with its redirect URI. Fanaura returns a client ID.3
Send the user to sign in
Open
https://app.fanaura.com/oauth/mcp/authorize with PKCE (S256). The user signs in and taps Allow access.4
Exchange the code
POST https://app.fanaura.com/api/oauth/mcp/token. Send the access token as Authorization: Bearer on every MCP request.Allowed return addresses
Fanaura only sends a sign-in back to addresses it trusts. Desktop clients work because they return to the same computer.MCP Registry
Fanaura is not listed in the official MCP Registry yet. Addhttps://app.fanaura.com/mcp to your client directly.
Test it from the terminal
You can confirm the server answers before you set up a client. Without a token, a401 is the correct answer.

