Skip to main content
Register an MCP server for an internal system or external service, and the AI can call its tools. Register it via “Add MCP” on the Connectors page (Sidebar > Configure).
Jinba App Neo supports http-stream type MCP servers. stdio type (locally executed) servers cannot be registered. Configurations that go through mcp-remote can be converted via JSON paste.
Your organization’s policy may block custom connectors. If you see “Your organization has blocked custom connectors (MCP).”, registration is unavailable — contact your organization’s administrator.

​
Registering with manual entry

1

Enter the server details

  • Name — e.g., Internal Wiki MCP
  • Server URL — the MCP server’s endpoint
  • Description (optional) — what the server provides
2

Set headers (optional)

For servers that require authentication, set request headers (e.g., Authorization: Bearer ...). Headers are sent to the server with every request.
3

Register

Press “Register.” Once registered, the tools can be called from chat.
The server URL must be a public URL reachable from Anthropic’s cloud. localhost and internal-network-only addresses (RFC1918) will not work.

​
Registering by pasting JSON

You can paste Claude Desktop-style mcpServers JSON as-is.
  1. Select the “Paste JSON” tab
  2. Paste JSON with a url entry, or with args that go through mcp-remote (one server at a time)
  3. Press “Apply to form” to load the parsed result into the form, then review and register

​
After registering

Right after registration, the connection may not have been verified yet (you will see “MCP created (connection unverified)”). Check that the tool list loads and that you can run a tool manually from the tool detail screen.

​
Editing and deleting

  • Edit — you can change the name, URL, and description. Saved header values are not displayed; to change them, check “Overwrite saved headers” and re-enter them
  • Delete — deleting an MCP also deletes its registered tools
Editing a workspace-shared MCP affects every other agent it is attached to.

​
Agent-specific MCP

Register an MCP for a single agent from the External connectors section of the agent’s configuration panel.
  • It does not appear in the Connectors page list
  • Authentication tokens can be specified as key references to Vault or Secret Manager instead of literal values (so the token itself is never stored)