Registering the Bareun connector in Claude (web)

If you register the Bareun MCP server as a custom connector in the Claude web app (and Claude Desktop), Claude calls Bareun directly during a conversation to perform Korean morphological analysis and spell checking. You can also publish the connector so that a team or organization can use it together.

What you need

A Bareun API key: for issuing keys and usage, see Using the cloud.
The endpoint address: for Bareun cloud it is https://api.bareun.ai:443/mcp. If you installed the spell checker yourself, use the externally reachable https address of that server plus /mcp. MCP is offered only in Bareun builds that include the spell checker, and installations for morphological analysis only do not have /mcp.

Custom connectors depend on your plan

Custom connectors, which let you add a remote MCP server yourself, and the organization publishing feature differ in menu location and availability by Claude plan (individual, Team, Enterprise, and so on). If you do not see the menu, check whether your plan supports the feature.

How to register

Do this in a web browser. You do not write the key in the settings; you enter it once in the login window after adding the connector.

In the Claude web app, go to Settings → Connectors.
Select Add custom connector.
Enter the values below and add it.
- Name: Bareun (or any name you like)
- Remote MCP server URL: https://api.bareun.ai:443/mcp
Click Connect on the connector you added, and a login window opens. Enter your Bareun API key there to log in.
When login succeeds, Bareun's tools (analyze_syntax, tokenize, list_pos_tags, correct_grammar) are registered.

The value you enter in the login window = your Bareun API key

Bareun identifies users by API key. So the value you enter in the connector login window is your Bareun API key. After you log in once, the credentials are kept, so you do not need to enter them again next time.

Publishing to your organization

On Team and Enterprise plans, you can publish the Bareun connector you added to organization members so that each member can easily turn on the same connector.

An organization admin (or the person who created the connector) publishes the Bareun connector to the organization under Settings → Connectors. After publishing, members turn on Bareun in their own connector list and each logs in with their own Bareun API key.
Usage is counted per API key used for login, so we recommend that each member log in with their own key.

Check before publishing

Publishing lets organization members see this connector. The API key itself is not published; each member logs in with their own key when they connect. Do not share one key among several people; issue and use one per member.

Verifying the connection

If you see Bareun and the four tools in the tools/connectors menu of the chat input or under Settings → Connectors, it is connected.
If you ask something like "Correct this sentence with Bareun," Claude calls Bareun.

Troubleshooting

What do I enter in the login window? Enter your Bareun API key (how to get one).
Getting an authorization error (401)? Check that the key you entered is correct and valid. If you disconnect the connector once and log in again, it reconnects cleanly.
Can't connect, or don't see the tools? Check that /mcp is at the end of the address, and try connecting again after a moment. For an on-premises server, check that it is an externally reachable https address (browser-based connectors may not be able to connect to plain http or private addresses).

Frequently asked questions

Enter your Bareun API key. Bareun identifies users by API key, so the value you enter in the login window is the API key. After you log in once, the credentials are kept.

Q. Can I publish it so the whole organization uses it together?

On Team and Enterprise plans, you can publish the Bareun connector to the organization. Even when published, the API key is not shared, and each member logs in with their own Bareun API key. Usage is counted per key, so we recommend issuing and using a key for each member.

Q. Can I add it the same way in the Gemini and ChatGPT web chat windows?

ChatGPT works. If you turn on Developer mode in settings, you can add the Bareun server address directly as a custom connector (ChatGPT registration guide). The Gemini web chat window does not yet offer a setting for entering an arbitrary MCP server address. In such environments, either integrate directly in code or use a tool that supports custom connectors (Claude, ChatGPT, Cursor, VS Code, and so on).

Q. Does it work in the Claude Desktop app too?

Yes. You can add it the same way from the connectors menu of Claude Desktop. For detailed instructions, including the config file (mcp-remote) method, see the Claude Desktop page.