Connect your assistant

There are two ways to connect. Use sign-in wherever your assistant offers it; use an API key for tools configured by file.

	Sign in with Reigniter	API key
Works in	claude.ai, Claude Desktop, ChatGPT, Cursor, VS Code, most modern clients	Anything that can send a header: Claude Code, Cursor, scripts
You do	Paste the address, sign in, click Allow	Create a key, paste it into the client’s config
Shows on your API keys page as	“Connector: Claude” (or the assistant’s name)	The name you gave the key

Both need the Agency plan. Revoke either on the API keys page and the assistant loses access at once.

Sign in with Reigniter

Claude (web and desktop)

1. Open Settings → Connectors and choose Add custom connector.
2. Name it Reigniter and paste https://reigniter.ai/mcp.
3. Click Add, then Connect.
4. Sign in to Reigniter if asked, check what it can do, and click Allow.
5. In a chat, turn the Reigniter connector on and ask for a video.

ChatGPT

1. Open Settings → Connectors. Depending on your ChatGPT plan, custom connectors may need developer mode switched on.
2. Create a connector with the URL https://reigniter.ai/mcp and OAuth authentication.
3. Connect, sign in to Reigniter and click Allow.

Cursor / VS Code

Add the server by URL. Both open the Reigniter sign-in in your browser the first time.

{
  "mcpServers": {
    "reigniter": { "url": "https://reigniter.ai/mcp" }
  }
}

In VS Code the file is .vscode/mcp.json and the key is servers instead of mcpServers.

Use an API key

1. Open the API keys page, create a key (for example “Claude Code”) and copy it. It is shown once.

2. Give it to your client as a Bearer token:

   claude mcp add --transport http reigniter https://reigniter.ai/mcp \
     --header "Authorization: Bearer emp_YOUR_KEY"

   Or in a config file:

   {
     "mcpServers": {
       "reigniter": {
         "url": "https://reigniter.ai/mcp",
         "headers": { "Authorization": "Bearer emp_YOUR_KEY" }
       }
     }
   }

3. Ask your assistant to “check my Reigniter account”. It should reply with your plan and credits.

Caution

A key spends your credits. Keep it out of shared files and repositories, and revoke it if it leaks.

Technical details

• Transport: Streamable HTTP, POST https://reigniter.ai/mcp, stateless.
• Authorization: OAuth 2.1 with PKCE (S256) and dynamic client registration, per the MCP authorization specification. Discovery: https://reigniter.ai/.well-known/oauth-protected-resource/mcp and https://reigniter.ai/.well-known/oauth-authorization-server.
• The access token a connector receives is an ordinary Reigniter API key, so everything above about keys applies to it.