Neonloops MCP MCP server

The Neonloops MCP server allows AI agents to interact directly with the Neonloops workspace without switching to the browser. It enables users to build, run, and check agentic workflows, approve or reject pending steps, and read or edit tables. The server integrates with major AI clients like Claude, Codex, ChatGPT, and Cursor, using OAuth or personal tokens for authentication while maintaining the same workspace data and run history as the web application.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by Neonloops

MCP endpoint (Streamable HTTP)

https://app.neonloops.com/api/mcp/v1

Vendor documentation

What you can do with it

Build and run agentic workflows
Approve or reject workflow steps
Read and edit workspace tables
Check run history and status

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http neonloops-mcp https://app.neonloops.com/api/mcp/v1

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add neonloops-mcp --url https://app.neonloops.com/api/mcp/v1

Cursor

Merge this server into .cursor/mcp.json in your project, then enable neonloops-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "neonloops-mcp": {
      "url": "https://app.neonloops.com/api/mcp/v1"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "neonloops-mcp": {
      "type": "streamableHttp",
      "url": "https://app.neonloops.com/api/mcp/v1",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start neonloops-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "neonloops-mcp": {
      "type": "http",
      "url": "https://app.neonloops.com/api/mcp/v1"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http neonloops-mcp https://app.neonloops.com/api/mcp/v1

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "neonloops-mcp": {
      "url": "https://app.neonloops.com/api/mcp/v1"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "neonloops-mcp": {
      "serverUrl": "https://app.neonloops.com/api/mcp/v1"
    }
  }
}

See all 1,687

Do you run Neonloops MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing