Registering Bareun in other MCP clients

Most MCP clients not covered separately here (Windsurf, Gemini CLI, JetBrains AI Assistant, and others) connect in the same way. There are only two common principles.

• Endpoint: Bareun cloud https://api.bareun.ai:443/mcp, or, if you installed the spell checker yourself, /mcp on that server's address (for example, http://localhost:5656/mcp). MCP is offered only in Bareun builds that include the spell checker (installations for morphological analysis only do not have it), and the address must end with /mcp.
• Authentication: Your Bareun API key in the api-key header (or Authorization: Bearer <key>). For a client that supports OAuth login, you log in on first connection by entering your Bareun API key in the browser.

If the client supports remote HTTP servers

In the settings, choose the HTTP (Streamable HTTP) server type and enter the URL and the api-key header. Many clients use the JSON form below (the key name differs slightly by tool, such as mcpServers or servers).

{
  "mcpServers": {
    "bareun": {
      "url": "https://api.bareun.ai:443/mcp",
      "headers": { "api-key": "YOUR_API_KEY" }
    }
  }
}

If the client supports only command-based (stdio) servers

For clients that cannot connect to remote HTTP directly, register the mcp-remote bridge as a command-based server (Node.js required). The bridge handles the HTTP connection and authentication for you.

{
  "mcpServers": {
    "bareun": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.bareun.ai:443/mcp", "--header", "api-key: YOUR_API_KEY"]
    }
  }
}

Testing the connection (for developers)

To quickly check the endpoint before registering it, you can use the official MCP Inspector (Node.js required).

npx @modelcontextprotocol/inspector

On the screen, set Transport to Streamable HTTP and URL to the endpoint (.../mcp), and put api-key: YOUR_API_KEY in the headers. When you connect, you see the list of tools and resources, and you can click each tool to call it.

Troubleshooting

• Don't see the tools? Check that /mcp is at the end of the address and that you chose the HTTP (Streamable HTTP) server type.
• Authorization error (401)? Check that the real key is in the api-key header (or Authorization: Bearer <key>).
• No spelling correction tool? MCP is offered only in Bareun builds that include the spell checker.

Frequently asked questions

Q. Can I use the Bareun MCP server with a client that is not on the list?

In most cases, yes. If the client supports remote HTTP (Streamable HTTP) servers, register it directly with the URL and the api-key header; if it supports only command-based (stdio) servers, connect through the mcp-remote bridge.

Q. Where do I find the endpoint address?

For Bareun cloud it is https://api.bareun.ai:443/mcp. If you installed the spell checker yourself, append /mcp to the address where that server is open (for example, http://localhost:5656/mcp). MCP is offered only in Bareun builds that include the spell checker, and installations for morphological analysis only do not have /mcp.