MCP (ChatGPT, Claude & CLI agents)
Sharick speaks the Model Context Protocol (MCP), so AI tools you already use — ChatGPT, Claude, or coding agents like Claude Code and Codex — can read and write your Sharick todos, notes, briefings, and calendar on your behalf.
Everything connects through your own Sharick account: whatever the AI does via MCP, it does as you, in your workspace.
Prerequisites
Section titled “Prerequisites”- A Sharick account with an active subscription — sign up at app.sharick.ai (Google sign-in supported).
- For ChatGPT / Claude: nothing else. Authentication is OAuth — no API key.
- For CLI agents (Claude Code, Codex): Node.js 20+ and an MCP API key (created in Step 1 of that section below).
Connect ChatGPT
Section titled “Connect ChatGPT”-
In ChatGPT, open Plugins (プラグイン) in the sidebar and click the + button to add one. (In older versions this lives under Settings → Connectors.)
-
Set the MCP server URL to:
https://app.sharick.ai/api/v1/mcp -
Choose OAuth as the authentication method.
-
A Sharick login page opens in your browser. Sign in with your Sharick account and approve the connection.
That’s it — ChatGPT can now work with your Sharick data.
Connect Claude (claude.ai)
Section titled “Connect Claude (claude.ai)”Same URL, same flow:
- In Claude, go to Settings → Connectors → Add custom connector.
- Enter
https://app.sharick.ai/api/v1/mcpas the server URL. - Sign in to Sharick when the browser window opens and approve.
Connect a coding agent (Claude Code / Codex)
Section titled “Connect a coding agent (Claude Code / Codex)”CLI agents authenticate with an API key instead of OAuth:
-
In Sharick, open Settings → MCP API Keys (web app) or Settings → Integrations → MCP (desktop app) and create a key. It starts with
mcp_and is shown only once — copy it right away. -
In a terminal, run:
Terminal window npx @sharick/cli loginand paste the key when prompted.
-
Install the MCP server and agent hooks:
Terminal window npx @sharick/cli install -
Verify:
Terminal window npx @sharick/cli status
Keep the key secret — anyone holding it can act as you. You can revoke or regenerate it from the same settings page at any time.
Verify it worked
Section titled “Verify it worked”Ask your connected AI something only Sharick can answer — for example,
“What’s on my Sharick todo list?” If it lists your actual todos, the
connection is live. For CLI setups, npx @sharick/cli status shows the
same thing from the terminal.
Other MCP clients
Section titled “Other MCP clients”For one-tap mobile delegation and reporting results back, follow the OpenClaw setup guide.
Any MCP client that supports Streamable HTTP can connect to
https://app.sharick.ai/api/v1/mcp, either through the OAuth flow above or
by sending an API key in an x-api-key (or Authorization: Bearer)
header.
Troubleshooting
Section titled “Troubleshooting”The OAuth window says I’m not authorized (401)
Section titled “The OAuth window says I’m not authorized (401)”MCP connector access requires an active subscription. Sign in at app.sharick.ai and check your plan.
My API key stopped working
Section titled “My API key stopped working”Keys can be revoked or regenerated — each regeneration invalidates the old
key everywhere it was used. Create or copy a fresh key from Settings →
MCP API Keys and run npx @sharick/cli login again.
The connector connects but tools fail
Section titled “The connector connects but tools fail”Run npx @sharick/cli doctor (for CLI setups) to check the installation,
or remove and re-add the connector (for ChatGPT / Claude) to refresh the
OAuth token.