Connect your AI tool
Every block on this page is what Sharek generates for you. You can copy them from here, or open Settings, then Developers, in Sharek and copy them from the MCP Client Configuration card.
Not on every plan. The Developers tab appears only when your plan includes the public API. See pricing. Signing in with Sharek needs neither the tab nor a key.
There are two ways to connect, and that card has a switch for each:
- Sign in with Sharek (no API key). Your tool opens Sharek, you sign in and press Authorize, and it is connected. No key sits in a file. This is the default, and the one to use unless your tool cannot sign in.
- API key. The key goes in your tool’s configuration. Use it for tools that cannot sign in, and for scripts and agents that run without you.
Claude: sign in with your Sharek account
Section titled “Claude: sign in with your Sharek account”Claude on the web, desktop and mobile connects to Sharek without a key: you add Sharek as a custom connector with this address, then sign in with your Sharek account.
https://dash.sharek.app/mcp-oauth-dynamic- On a personal plan (Free, Pro, Max or Ultra): in Customize, then Connectors, select Add, then Add custom connector. Enter a name and the address, select Continue, then Add, and select Connect to sign in. Claude’s Free plan allows one custom connector.
- On a Team or Enterprise plan: an Owner opens Organization settings, then Connectors, and selects Add, then Custom (and Web, if Claude asks for the type). They enter a name and the address and select Add. Members then find Sharek under Customize, then Connectors, and select Connect.
When you select Connect, sign in to Sharek if it asks, then approve the access Claude requests. If Claude asks for authentication settings, keep the ones it marks Detected. For the OAuth client, Register automatically works with Sharek.
Claude reaches only the Sharek organization you had open when you pressed Authorize: its channels, posts and media. To disconnect, open Sharek under Customize, then Connectors, and select Disconnect, or Remove from its three-dot menu. You can also revoke Claude under Settings → Apps → Approved Apps in Sharek.
For what to ask once it is connected, see Sharek for Claude on sharek.app.
ChatGPT
Section titled “ChatGPT”ChatGPT on the web adds Sharek as a plugin.
-
Go to ChatGPT Plugins, select the plus button, then Add custom MCP server.
-
Enter a name, such as Sharek. Under Connection, paste this address as the Server URL.
https://dash.sharek.app/mcp-oauth-dynamic -
Choose OAuth for authentication, review the risk warning, and select I understand and want to continue, then Create as a plugin.
-
Install the plugin before you use it. You find it in your personal plugins, or in the workspace where you created it.
-
In a chat, type
@in the prompt box and select your Sharek plugin.
When ChatGPT sends you to Sharek to connect, sign in and press Authorize.
This works on ChatGPT plans that allow custom MCP servers, and a workspace’s permissions can limit it. To disconnect, revoke ChatGPT under Settings → Apps → Approved Apps in Sharek.
For what to ask once it is installed, see Sharek for ChatGPT on sharek.app.
Command line tools, editors and agents
Section titled “Command line tools, editors and agents”Every tab has both versions. With Sign in with Sharek, most tools open a browser the
first time they connect, so you can sign in and press Authorize; a tab that needs one
more step says so. With an API key,
put your real key in place of your-api-key (see use an API key).
Note the Bearer prefix: the MCP blocks carry it, and the public API
refuses it.
Run this command in your terminal.
Sign in with Sharek
claude mcp add sharek --transport http "https://dash.sharek.app/mcp-oauth-dynamic"Then start Claude Code, run /mcp, select sharek and choose Authenticate, or run
claude mcp login sharek in your terminal.
API key
claude mcp add --transport http sharek https://dash.sharek.app/mcp --header "Authorization: Bearer your-api-key"Add to .cursor/mcp.json in your project root.
Sign in with Sharek
{ "mcpServers": { "sharek": { "url": "https://dash.sharek.app/mcp-oauth-dynamic" } }}API key
{ "mcpServers": { "sharek": { "url": "https://dash.sharek.app/mcp", "headers": { "Authorization": "Bearer your-api-key" } } }}Add to .vscode/mcp.json in your project root.
Sign in with Sharek
{ "servers": { "sharek": { "type": "http", "url": "https://dash.sharek.app/mcp-oauth-dynamic" } }}API key
{ "servers": { "sharek": { "type": "http", "url": "https://dash.sharek.app/mcp", "headers": { "Authorization": "Bearer your-api-key" } } }}VS Code also reads a .mcp.json file in your project root, where the same entry goes
under mcpServers instead of servers.
Devin Desktop was called Windsurf. Add to ~/.codeium/windsurf/mcp_config.json.
Sign in with Sharek
{ "mcpServers": { "sharek": { "serverUrl": "https://dash.sharek.app/mcp-oauth-dynamic" } }}API key
{ "mcpServers": { "sharek": { "serverUrl": "https://dash.sharek.app/mcp", "headers": { "Authorization": "Bearer your-api-key" } } }}Devin Desktop imports this Windsurf file by default. Its own files are
.devin/mcp_config.json in a project and ~/.config/devin/mcp_config.json for all your
projects, where a server takes url with "transport": "http", plus headers for a key.
To check that Sharek loaded, click Customize in the agent sidebar, then MCPs, and look under This computer. If it shows Needs authentication, click Authenticate.
Sign in with Sharek: run this command in your terminal.
amp mcp add sharek https://dash.sharek.app/mcp-oauth-dynamicAPI key: add to your Amp settings.json.
{ "amp.mcpServers": { "sharek": { "url": "https://dash.sharek.app/mcp", "headers": { "Authorization": "Bearer your-api-key" } } }}Sign in with Sharek: add to ~/.codex/config.toml, then run codex mcp login sharek.
# ~/.codex/config.toml
[mcp_servers.sharek]url = "https://dash.sharek.app/mcp-oauth-dynamic"API key: add to ~/.codex/config.toml.
# ~/.codex/config.toml
[mcp_servers.sharek]url = "https://dash.sharek.app/mcp"http_headers = { "Authorization" = "Bearer your-api-key" }Add to ~/.gemini/settings.json.
Sign in with Sharek
{ "mcpServers": { "sharek": { "url": "https://dash.sharek.app/mcp-oauth-dynamic" } }}If no browser opens when Gemini CLI first connects, run /mcp auth sharek in Gemini CLI.
API key
{ "mcpServers": { "sharek": { "url": "https://dash.sharek.app/mcp", "headers": { "Authorization": "Bearer your-api-key" } } }}Go to Settings > Agents > MCP servers > + Add, then paste this config.
Sign in with Sharek
{ "sharek": { "url": "https://dash.sharek.app/mcp-oauth-dynamic" }}API key
{ "sharek": { "url": "https://dash.sharek.app/mcp", "headers": { "Authorization": "Bearer your-api-key" } }}Add to ~/.hermes/config.yaml, then run /reload-mcp in the chat.
Sign in with Sharek
# ~/.hermes/config.yaml
mcp_servers: sharek: url: "https://dash.sharek.app/mcp-oauth-dynamic" auth: oauthAPI key
# ~/.hermes/config.yaml
mcp_servers: sharek: url: "https://dash.sharek.app/mcp" headers: Authorization: "Bearer your-api-key"Sign in with Sharek: run this command in your terminal.
openclaw mcp add sharek --url https://dash.sharek.app/mcp-oauth-dynamic --transport streamable-http --auth oauth && openclaw mcp login sharekAPI key: add to ~/.openclaw/openclaw.json.
{ "mcp": { "servers": { "sharek": { "url": "https://dash.sharek.app/mcp", "transport": "streamable-http", "headers": { "Authorization": "Bearer your-api-key" } } } }}Run this in your terminal, with <group-id> replaced by the agent group that should get
Sharek. NanoClaw has no header option, so the API key version carries the key in the
address.
Sign in with Sharek
ncl groups config add-mcp-server --id <group-id> --name sharek --url https://dash.sharek.app/mcp-oauth-dynamicAPI key
ncl groups config add-mcp-server --id <group-id> --name sharek --url https://dash.sharek.app/mcp/your-api-keyFor what to ask once you are connected, sharek.app has a page for Cursor, VS Code, Devin Desktop, Codex and Gemini CLI.
Use an API key
Section titled “Use an API key”Open Sharek and go to Settings.
-
Open Developers, then the MCP Client Configuration card.
-
Switch Authentication to API Key, pick your client, press Reveal, and Copy. That gives you the block above with your real key in place of
your-api-key.
If you would rather assemble it yourself, take the key from the API Key card in the same Developers section, as described in authentication, and paste it into one of the blocks above.
Clients that take only a URL
Section titled “Clients that take only a URL”Some clients do not let you set headers. They take a URL and nothing else. For those, Sharek carries the key in the address instead:
https://dash.sharek.app/mcp/your-api-keyClaude and ChatGPT accept this address too, but signing in (above) keeps the key out of their settings.
Chat-only agents
Section titled “Chat-only agents”Some agents have no MCP or tool settings at all. Paste this into the chat instead: the agent installs the Sharek CLI and asks you for your API key.
Install the Sharek CLI with `npm install -g sharek-cli`, then install the Sharek skill with `npx skills add sharekhq/sharek-agent`. Ask me for my Sharek API key and set it as the SHAREK_API_KEY environment variable before using the CLI.Check that it worked
Section titled “Check that it worked”Ask your assistant to list your Sharek channels. A working connection answers with the channels you have connected, by name.
If it does not:
- The server is missing from the tool’s list. The configuration file was not picked
up. Most clients need a restart after the file changes, and most show connected
servers somewhere in their interface: look for
sharekor Sharek MCP. - Signing in did not finish. Remove Sharek from your tool and add it again with the sign-in address above. Sign in to Sharek, open the organization whose channels you want, and press Authorize.
- It fails to connect, or asks you to sign in. With an API key, Sharek refused the key: it is wrong, incomplete, or was rotated. Copy the block again from the app rather than editing the one you have, and check your credentials to test the key on its own.
- It lists no channels at all. The connection is fine and the account genuinely has none. Connect a channel first.
Where to go next
Section titled “Where to go next”- Tool reference for what your assistant can actually call.
- Examples for conversations that work.