Grounds Claude Code in your Clawnify organization and lets it act on the platform — retrieve your company knowledge, read a client's project reference, recall durable facts, and deploy apps and agents — without leaving your terminal.
The plugin itself is thin. It holds no knowledge: everything is retrieved on query from your org-scoped Clawnify MCP endpoint, authenticated as you. Your knowledge stays server-side and org-scoped; the plugin just wires it into Claude Code and teaches the agent when to reach for it.
- Your org's Clawnify MCP wired in as one server (
mcp__clawnify__*): company knowledge, project reference, memory, product docs, and app/agent deploy tools. - The
clawnify-knowledgerouter skill — teaches the agent which source answers which kind of question (platform how-to vs. your company facts vs. a specific client vs. third-party docs vs. this repo's code).
| Scope | What it is | Tool |
|---|---|---|
| Clawnify product docs | How to use the platform — deploy an app, provision an agent, connections | clawnify_docs_search |
| Your org corpus | Your company's own brand / pricing / policy / SOP, and per-client project reference | company_knowledge_*, projects_*, memory_* |
Company knowledge is a versioned wiki — cite grounded answers as Per <Title> v<N>. It never holds secrets or per-customer facts.
# In Claude Code:
/plugin marketplace add clawnify/code-plugin
/plugin install clawnify-codeOn first use, Claude Code discovers the auth server (OAuth, RFC 9728) and prompts you to sign in with your Clawnify account. The token identifies your organization — no org id or secret is stored in the plugin.
Multiple organizations? The default endpoint (https://mcp.clawnify.com/mcp) resolves your single org from the token. If you belong to more than one, point the server at your org's handle URL — https://mcp.clawnify.com/c/<handle>/mcp — in .claude-plugin/plugin.json (find your handle in the dashboard).
- Retrieval, not bundling. No knowledge ships in this repo. Every fact is fetched live, scoped to your org, as you.
- Org isolation. Requests are authorized by your token; cross-org access returns
404— existence is never disclosed across org boundaries. - The client-facing product-docs corpus is curated and separate from Clawnify's internal knowledge — no internal strategy, pricing internals, or codenames.
MIT © Clawnify