Connect · Other MCP clients
Étincel isn't Claude-only.
It's a standard remote MCP server: Streamable HTTP transport, OAuth 2.1 for auth, nothing Claude-specific in the protocol. Cursor, ChatGPT/Codex connectors, or any other client that speaks MCP can point at the same URL and call the same tools.
MCP server URL
https://etincel.ai/api/mcpPoint your client at the server
Add the URL above as a remote MCP server wherever your client configures those, most tools use a JSON config that looks like this.
{
"mcpServers": {
"etincel": {
"url": "https://etincel.ai/api/mcp"
}
}
}
Sign in
The first call to a tool triggers OAuth. A browser tab opens to sign in with your Étincel account, the same account regardless of which client is asking. Approve it once and the client keeps the token for next time.
Use it
Ask for a draft in your voice, an email, a PR description, a blog post, whatever you'd normally ask for. The client reaches for get_style_guide the same way Claude does.
Clients this works with
- Cursor
- Add it under Settings → MCP as a remote server with this URL. Cursor handles the OAuth handshake itself.
- ChatGPT / Codex
- Add it as a connector pointed at this URL, wherever your OpenAI client exposes remote MCP servers.
- Windsurf, other MCP clients
- Any client built against the Model Context Protocol's Streamable HTTP transport and OAuth spec can connect the same way.
Using Claude instead?