onboarding

Onboarding

The Intelligo plugin connects to a remote MCP server hosted on Cloudflare Workers at:

https://intelligo-mcp.intelligo-254.workers.dev/mcp

The server speaks OAuth 2.1 with PKCE plus an extra shared demo-password gate during sign-in. This skill walks the user through first-time setup and the most common failures.

First-time setup

1. Install the plugin. In Claude Cowork: Customize → "+" next to Personal plugins → Create plugin → Add marketplace → enter "intelligogroup/claude-plugin" → Sync → install the "intelligo" plugin.

2. Enable it. The plugin appears under Personal plugins. Click it, toggle Enabled.

3. Sign in. The first time Claude calls getSchema or queryIntelligo, Claude Desktop opens an OAuth login page hosted by the Worker. Two fields:

   • Email — used as your identity (logged on every tool call as email=...).
   • Demo password — the shared password for this demo deployment.

   Get the demo password from the Intelligo team (Slack / email). It is not your real Intelligo account password.

4. Approve the OAuth consent screen. Claude Desktop is granted scoped access; tokens are stored locally by Claude.

Troubleshooting

"401 Unauthorized" / browser keeps reopening login

• Wrong demo password. Re-enter it. Timing-safe comparison means typos always fail.
• Token expired. Disable + re-enable the plugin in Customize to force a fresh OAuth flow.

"MCP server not reachable" / connection error

• Check the Worker is up: curl https://intelligo-mcp.intelligo-254.workers.dev/health should return 200.
• Corporate VPN / firewall may block *.workers.dev. Try off-VPN to confirm.
• The plugin uses type: "http" (streamable-HTTP transport). Older Claude Desktop versions without HTTP transport support will fail — update Claude Desktop.

Tool calls succeed but return "Type X not found"

• The schema may not have that type. Run getSchema with no args once to see the full SDL, then use the correct type name.

"Query exceeds 8192-byte limit"

• The Worker rejects oversized queries to protect itself. Narrow the selection set or split into multiple calls.

Wrong email in logs

• The OAuth Props.email is whatever you typed at sign-in. To change identity, disable + re-enable the plugin and sign in again with the right email.

What this plugin does NOT do

• It does not connect to a real Intelligo production tenant. The data is mocked (seeded fixtures in the Worker).
• It does not persist user data between sessions.
• It does not validate the demo password against any real auth system — the password is a single shared gate.

Where the source lives

• Plugin marketplace + skills: https://github.com/intelligogroup/claude-plugin
• MCP Worker: ask the Intelligo team for the worker repo URL.