KnitKnot
You are reading the agent-optimized layer of this page: the literal markdown we serve to AI crawlers and assistants, shipped in the page source of every visit. Making sure AI reads the right facts about a company is literally what KnitKnot does.

# KnitKnot workspace MCP and integrations

Query authorized workspace evidence from an MCP-capable assistant and connect supported team and analytics tools.

## Workspace MCP

KnitKnot exposes a curated set of tools over the same authorized workspace data used by the console. Supported tools cover competitive position, issues and their evidence, playbooks, sources, demand topics, questions, coverage, and workspace context. Supported playbook status changes appear in the console.

This authenticated workspace service is separate from the rollout-gated read-only MCP interface on managed customer domains. The customer-domain interface reads published page, search, and approved-fact artifacts.

## Supported connections

  • - Notion coordinates the playbook backlog in a connected database.
  • - GitBook stores the configured documentation destination.
  • - Google Analytics adds observed AI-referred sessions and landing pages beside benchmark trends. Referral data is directional and remains separate from benchmark scoring.

## Access

Interactive MCP clients can use OAuth 2.1. Scripts and non-interactive clients can use a KnitKnot API key. Every request is scoped to the caller's authorized workspace, and customer-visible tools are controlled by an explicit allowlist.

## Related pages

Raw mirror of this content: https://knitknot.ai/product/mcp-integrations.md. Site-wide summary: /llms.txt · full content: /llms-full.txt

MCP & Integrations

Bring KnitKnot evidence into the tools where work happens.

Use the authenticated workspace MCP to inspect evidence and manage supported playbook states. Connect team and analytics tools for the narrower jobs they own.

Product evidence plate
Workspace MCP Authenticated · workspace scoped

Request

Which issue reaches the most buyer answers, and what work is linked to it?

list_issues

Returns the ranked issue index for the authorized workspace.

get_issue

Opens the selected issue, its evidence, and linked playbooks.

AI repeats an outdated deployment limitation

14 affected answers · 2 linked playbooks · evidence available

Two MCP surfaces

Workspace access and published-page access have different jobs.

The authenticated workspace service is available for assistant workflows. Customer-domain MCP remains a rollout-gated publishing interface.

Surface Reads Access Primary use
Workspace MCP Authorized workspace evidence and supported work records OAuth 2.1 or API key Research and supported playbook coordination
Customer-domain MCP Published pages, search artifacts, and approved facts Read-only and rollout-gated Agent access to the published corpus
Connections

Each integration owns a narrow part of the workflow.

Notion

Coordinate the playbook backlog

Use a connected database for team review while supported playbook status changes stay tied to the KnitKnot record.

GitBook

Set the documentation destination

Validate the connection and select the workspace destination used by the documentation workflow.

Google Analytics

Add observed AI referral data

Show recognized AI-referred sessions and landing pages beside the benchmark without adding them to the score.

Access

Use the credential that matches the client.

Interactive clients use the signed-in account. Programmatic clients use an API key. Both resolve against the caller's authorized workspace.

OAuth 2.1

Approve an interactive MCP client with the same KnitKnot account used for the console.

API key

Authenticate scripts and other non-interactive clients without a browser approval flow.

Read the MCP setup guide
Questions

MCP and integrations FAQ

Start with the record

Connect the workspace without splitting the record.

Use MCP for assistant workflows and the console for benchmark execution, dense review, configuration, and publishing.

Question → evidence → next evaluation