What MCP servers add to a coding workflow
An MCP server is a program that exposes tools to an AI client, so the agent can act outside the chat: clip.qa exposes 15 tools for bug reports, and KnowMan exposes six tools for a knowledge base.
Two deployments appear here. clip.qa runs a remote server over Streamable HTTP, added by URL; KnowMan also ships a local stdio server, started by the client with npx -y @knowman/mcp (Node 22 or newer, MIT-licensed npm package). For working with notes over MCP, see connect any AI to your notes.
clip.qa: connect bug reports to your AI tool
clip.qa runs a remote MCP server over Streamable HTTP at https://mcp.clip.qa/mcp. Sign in through your browser on first use with OAuth 2.1 and PKCE. There is no SDK to install, and MCP access is included on every plan.
The server exposes 15 tools. An agent can list reports and retrieve report details with listReports and getDetails, search reports, retrieve report diffs and retrieve project summaries with searchReports, getReportDiff and getProjectSummary, and read the report, screenshots, video transcript, frame analysis and report diffs. For Chrome-extension reports, an agent can also read console logs and network requests.
Write actions need write scope: createComment, linkFix and linkFixAttempt. getProjectSummary requires project read scope. Reports remain private until explicitly shared, PII is scrubbed from MCP output, and video analysis runs in the cloud.
KnowMan: connect a knowledge base and memories
KnowMan saves articles and links, reads and tags them, answers questions with citations, and keeps memories such as claims, decisions and playbooks (KnowMan MCP). Its hosted MCP server runs at https://api.knowman.io/mcp over Streamable HTTP. The server is open source under MIT, package @knowman/mcp 0.3.0, run with npx -y @knowman/mcp on Node 22 or newer.
KnowMan's MCP server exposes six tools: kb_search (search saved items by keyword or meaning), kb_ask (answer with citations), kb_get_item (readable content of one item), kb_save (save a URL to Inbox or Knowledge Base), kb_recent (recent items), kb_memories (saved claims, decisions and playbooks, read-only).
Authentication is OAuth sign-in or an API key: the client opens a KnowMan consent page, you approve, or you send Authorization: Bearer <key>. Scopes are knowman.read for search, read and ask, and knowman.write for saving links. Access tokens last one hour and refresh automatically. The full flow, from registration through consent, token, tool calls and refresh, is verified with the official MCP SDK client. Setup details are in the MCP server guide.
Connect a hosted server by URL
For clients with MCP OAuth, add the server URL, sign in, approve. KnowMan needs an account at https://app.knowman.io (setup); its server URL is https://api.knowman.io/mcp (source). The clip.qa server URL is https://mcp.clip.qa/mcp (source).
Connect KnowMan with an API key: documented configs
Create a key in KnowMan settings; a key cannot create other keys. Alternatively run npx -p @knowman/mcp knowman login once: the saved credential is shared by the CLI and the MCP server, so the env block can be dropped.
Claude Code (documented config): claude mcp add --transport http knowman https://api.knowman.io/mcp --header "Authorization: Bearer <key>".
Cursor mcp.json (documented config): {"mcpServers":{"knowman":{"url":"https://api.knowman.io/mcp","headers":{"Authorization":"Bearer <key>"}}}}.
Claude Desktop, local stdio server (documented config): {"mcpServers":{"knowman":{"command":"npx","args":["-y","@knowman/mcp"],"env":{"KNOWMAN_API_KEY":"<key>"}}}}. The package requires Node 22 or newer. These are the documented client configurations.
Prompts that use the tools
Once connected, prompt the assistant directly: "search my KnowMan for ..." or "save this URL".
Against the clip.qa server, ask for recent reports, the console logs and network requests of a Chrome-extension report, or a report diff. Comment or link a fix with createComment, linkFix or linkFixAttempt under write scope.
Scopes, tokens, and disconnecting apps
KnowMan consent covers two scopes: knowman.read for search, read and ask, and knowman.write for saving links. Access tokens last one hour and refresh automatically.
To disconnect an app, delete its "OAuth: <app name>" entry in your KnowMan API-keys list; changing your password disconnects every app. clip.qa keeps reports private until explicitly shared and scrubs PII from MCP output.
clip.qa explains its side in two MCP servers for an AI coding workflow.
Questions people ask
What is an MCP server?
A server that exposes tools to an AI client, so the agent can act outside the chat. Remote servers run over Streamable HTTP and are added by URL; local stdio servers are started by the client, like npx -y @knowman/mcp.
Does clip.qa MCP need an SDK or a paid plan?
No. There is no SDK to install, and MCP access is included on every plan. Setup is the server URL https://mcp.clip.qa/mcp plus browser sign-in with OAuth 2.1 and PKCE.
How do I add KnowMan to my coding agent?
Add https://api.knowman.io/mcp and sign in with OAuth, or send an API key as Authorization: Bearer <key>. Documented configs (source) include claude mcp add --transport http knowman https://api.knowman.io/mcp --header "Authorization: Bearer <key>" for Claude Code, a Cursor mcp.json entry, and Claude Desktop with the local stdio server npx -y @knowman/mcp on Node 22 or newer.
How do I disconnect a connected app?
In KnowMan, delete the app's "OAuth: <app name>" entry in your API-keys list. Changing your password disconnects every app.