Files & tools

Integrations & MCP

Bringing outside tools into a workspace, and connecting outside agents to your workspace — with scopes you control.

CogniWork speaks the Model Context Protocol in both directions. It can use your tools, and it can be a tool.

Installing a server into a workspace

Find this under Integrations.

Add an MCP server by pointing CogniWork at it and supplying whatever credential it needs. Once installed, its tools become available to the assistant and to any worker you allow to use them.

Typical things people connect: an issue tracker, a CRM, a search provider, a document store, a payment system, an internal service their team already runs.

Setting one up

  1. Add the server — its address, and a name you’ll recognise.
  2. Provide its credential. Secrets are stored per workspace and are never shown back to you or included in chat transcripts.
  3. Review the tools it exposes. You can see exactly what the server offers before anything uses it.
  4. Decide who may use it — the assistant only, or specific workers too.

Using it

Just ask. “Which support tickets mention the outage?” reaches through the connected tracker. You can also bind a view component directly to a tool call, so a page shows live data from a system whose records never enter CogniWork at all.

Removing one revokes its credential and takes its tools away immediately. Anything built on it keeps working, minus that data source.

Your workspace as an MCP server

The other direction: point an MCP client — Claude Desktop, an IDE, your own agent — at CogniWork, and your workspace becomes a set of tools it can call. Read your data, create records, run a worker, render a view, all from outside the app.

Connecting

  1. Add CogniWork as an MCP server in your client, using the connection URL from the Integrations page.
  2. Your client sends you to CogniWork to sign in. Normal login, in your browser.
  3. Choose what this connection may reach: one workspace, several, or all of them.
  4. Approve. The client gets a credential scoped to exactly that choice.

What the scope means

The grant is a ceiling, not a suggestion. A client granted one workspace cannot reach a second one, even if you’re a member of it, and even if it asks. If you later leave a workspace, the grant stops working for it — your live membership is the floor.

Revoking

Revoke a connection from the Integrations page and it stops working immediately. Nothing that connection created is deleted; it simply loses its key.

Practical notes

  • One connection, many workspaces. If you granted several workspaces, your client chooses which one each call targets. Nothing silently falls back to a different workspace.
  • Credentials rotate. Long-lived connections refresh themselves. If a refresh is ever replayed by something that shouldn’t have it, the whole connection is revoked rather than quietly reissued.
  • Everything is metered. A tool call from outside that makes your workspace think counts against that workspace’s usage, the same as a chat turn.

Next