The neonloops MCP server
neonloops has an MCP server, so you can drive your workspace from the AI client you already use — Claude, Codex, ChatGPT, Cursor, or any other MCP client — instead of switching over to the browser.
What can I do with it?
Once a client is connected, you can ask it to build a workflow, run one, check what a run did, approve or reject a step it's waiting on, or read a table — the same things you'd do in the app, from wherever you're already working.
It reads and writes through the same workspace you use in the browser: a workflow it starts shows up in your run history, a table it edits is the table you see on your own screen.
ChatGPT and Codex use a connection with billing and secret-value entry reserved for the neonloops web app. Other MCP clients keep their existing connection.
How do I connect a client?
Claude
Signs in with your neonloops account — no token to copy.
- In claude.ai or Claude Desktop, open Settings → Connectors.
- Click "Add custom connector".
- Paste the MCP server URL.
- Sign in to neonloops when prompted and approve the connection.
https://app.neonloops.com/api/mcp/v1Claude Code
Needs a personal token from your neonloops workspace — or sign in over OAuth instead. Create a token in Settings → Connected agents
- Run `claude mcp add --transport http neonloops https://app.neonloops.com/api/mcp/v1 --header "Authorization: Bearer <your token>"`, using a token minted from Settings → Connected agents.
- Prefer OAuth instead? Run `claude mcp add --transport http neonloops https://app.neonloops.com/api/mcp/v1` with no header, then inside Claude Code run `/mcp` and complete the sign-in to neonloops.
claude mcp add --transport http neonloops https://app.neonloops.com/api/mcp/v1 --header "Authorization: Bearer <your token>"Codex
Signs in with your neonloops account — no token to copy.
- With the Codex CLI installed, run `codex mcp add neonloops --url https://app.neonloops.com/api/mcp/openai` in your terminal.
- Run `codex mcp login neonloops`, then sign in to neonloops in the browser and approve the connection.
- Start a new Codex session. If the server does not appear, reconnect or restart Codex to load it.
- Manage billing and enter secret values in the neonloops web app; these actions are not available through this connection.
codex mcp add neonloops --url https://app.neonloops.com/api/mcp/openai
codex mcp login neonloopsChatGPT
Signs in with your neonloops account — no token to copy.
- In ChatGPT, open Settings → Security and login and turn on Developer mode. Availability depends on your account and workspace policy.
- Open Plugins and select the plus button. Enter neonloops as the name, add a description, and paste the MCP server URL under Connection.
- Choose OAuth and, if asked for a registration method, choose Dynamic client registration. Create the connection, sign in to neonloops, and approve access.
- Start a new chat and select the neonloops connection from the tools menu.
- Manage billing and enter secret values in the neonloops web app; these actions are not available through this connection.
https://app.neonloops.com/api/mcp/openaiCursor
Needs a personal token from your neonloops workspace. Create a token in Settings → Connected agents
- Open (or create) `~/.cursor/mcp.json`.
- Add an entry under `mcpServers` with the server URL and an `Authorization` header carrying a token minted from Settings → Connected agents.
- Restart Cursor, or reload MCP servers, to pick up the new entry.
{
"mcpServers": {
"neonloops": {
"url": "https://app.neonloops.com/api/mcp/v1",
"headers": {
"Authorization": "Bearer <your token>"
}
}
}
}Other
Needs a personal token from your neonloops workspace — or sign in over OAuth instead. Create a token in Settings → Connected agents
- Point the client at the MCP server URL using Streamable HTTP transport.
- If the client supports OAuth, let it discover and complete the OAuth 2.1 sign-in automatically.
- Otherwise, set an `Authorization: Bearer <your token>` header using a token minted from Settings → Connected agents.
curl https://app.neonloops.com/api/mcp/v1 -H "Authorization: Bearer <your token>" -H "Content-Type: application/json"Where do I get a token?
Sign in to neonloops and open Settings → Connected agents. Name the agent, choose what it may do, and create the token — it is shown once, so copy it straight into your client.
That token is the only credential a client needs: when a client asks for an API key or a bearer token, this is what goes there. Clients that sign in over OAuth, like Claude, Codex, and ChatGPT, don't need one at all.
What can an agent do — and not do?
A newly connected agent can only see your projects, workflows and run history — nothing more. Anything that changes your workspace, like creating or running a workflow, has to be turned on explicitly, and the riskiest scopes — managing members, connected apps, or billing — are opted into one at a time, never as a bundle.
An action that can't be undone, like deleting something, asks twice: the agent has to show what it's about to do before a second call actually does it.
A token is shown once, expires in 7 days, and you can revoke it any time from Settings → Connected agents. Every call an agent makes is logged, so nothing it did is invisible after the fact.
What does neonloops record when an agent connects?
A log of what the agent did: which tool it called, when, and whether it worked. The values it sent aren't in that log, and the records stay with your workspace.
Beyond that, neonloops only receives the tool calls your client sends — not your conversation with it. The privacy policy has the full detail, including how long each record is kept.
Do I need to write code?
No. Connecting a client uses a settings screen or commands copied from this page or Settings → Connected agents. Once it's connected, you talk to it the same way you already talk to that client.
Is there a public API or SDK?
Not a REST API or SDK, no — the MCP server is the public interface today. If you want to script against neonloops directly rather than through an AI client, the MCP server is what's there.
Who do I ask if something doesn't work?
The address to write to is hi@neonloops.com. Tell us which client you're connecting from and what it showed you when it failed — the error your client displays is the most useful thing to paste.