Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.qoder.com/llms.txt

Use this file to discover all available pages before exploring further.

MCP (Model Context Protocol) is an open standard that lets AI applications plug into external tools and data sources through a unified interface. Think of it as USB-C for AI — just as USB lets any peripheral work out of the box, MCP gives AI a single way to talk to any external service. Out of the box, QoderWork can only work with what’s in your conversation. Add MCP, and it can manage your calendar, search your docs, pull live data, and much more — turning it from a chatbot into an assistant that actually gets things done.

​
How It Works

MCP follows a client-server model:
  • MCP Client — QoderWork itself. It sends requests and displays results.
  • MCP Server — A service deployed by a provider (Firecrawl, Slack, etc.) that performs specific operations and returns data.
You don’t need to worry about the plumbing. Just describe what you need in plain language, and QoderWork figures out which MCP tool to call, executes it, and weaves the result into the conversation.

​
Adding an MCP Server

Open the QoderWork desktop app and head to Settings → MCP Servers. Click + Add in the top-right corner — you’ll see two options.
mcp

​
Paste JSON Config

The fastest path if you already have a JSON config from an MCP marketplace or provider.
  1. Click + Add → Paste JSON Config.
  2. Paste the JSON configuration into the dialog.
  3. Click Import.
A typical config looks like this: 
{
  "mcpServers": {
    "service-name": {
      "type": "streamable-http",
      "url": "https://mcp-server-url.example.com/sse",
      "headers": {
        "Authorization": "Bearer your-token"
      }
    }
  }
}

​
Fill in Config Manually

Prefer filling things in yourself? Click + Add → Fill in Config Manually. In the Add MCP Server dialog that appears, start by selecting a Server Type from the dropdown. Each type shows a different set of fields:

​
Streamable HTTP / SSE

For remotely hosted MCP services accessed via URL. This is the most common type offered by MCP marketplaces — simple to configure and recommended as your first choice.
  • Server Name — A label you’ll recognize.
  • Server URL — The endpoint URL copied from the MCP marketplace.
  • Headers (Optional) — Authentication headers like Authorization: Bearer your-token. Click + Add Header to enter them manually, or Paste to bulk-import from your clipboard.
Streamable HTTP is the newer, more capable successor to SSE. When a marketplace provides a Streamable HTTP URL, choose that type.

​
STDIO

For locally running MCP servers launched via the command line. Best suited for developers working with local tools or CLI integrations. This requires the relevant runtime (Node.js, Python, etc.) to be installed on your machine.
  • Server Name — A label you’ll recognize.
  • Command — The full launch command, e.g., npx -y @modelcontextprotocol/server-filesystem.
  • Environment Variables (Optional) — Key-value pairs the service needs at runtime (API keys, access tokens, etc.). Add them one by one with + Add Variable, or click Paste to import in bulk.
Click Add when you’re done.
Paste JSON Config or Fill in Config Manually? Pasting JSON parses everything — type, URL, auth — in one shot. Filling in manually gives you field-by-field control. The end result is identical; pick whichever feels easier.

​
Managing MCP Servers

All your added servers appear under Custom Servers on the MCP Servers page. From here you can:
  • Toggle a server on or off.
  • Expand a server to see its available tools.
  • Edit or delete a server using the icons next to it.
Scroll down to the Built-in Servers section for MCP servers that ship with QoderWork (Browser, Notion, Linear, and more). These can be toggled on or off the same way.

​
Walkthrough: Connecting a Firecrawl MCP Server

Let’s walk through a real example — adding the Firecrawl MCP server so QoderWork can scrape web pages, crawl websites, and extract structured data from the internet on your behalf.

​
Step 1: Get the Config from an MCP Marketplace

  1. Open your browser and visit mcp.so.
  2. Search for Firecrawl and open the server detail page.
  3. Review the description and the list of supported tools to make sure it fits your needs.
  4. Locate the JSON Config block on the page and click Copy to copy the full configuration to your clipboard.
The copied content looks something like this: 
{
  "mcpServers": {
    "firecrawl-mcp": {
      "command": "npx",
      "args": ["-y", "firecrawl-mcp"],
      "env": {
        "FIRECRAWL_API_KEY": "fc-your-api-key"
      }
    }
  }
}
Firecrawl requires an API key. Sign up at firecrawl.dev to get one, then include it in the env field of your config.

​
Step 2: Add It to QoderWork

  1. Open the QoderWork desktop app and go to Settings → MCP Servers.
  2. Click + Add → Paste JSON Config.
  3. Paste the config into the dialog.
  4. Click Import.
Once added, the server appears under Custom Servers. A green dot next to the name means the connection is live. Expand the entry to browse its tools.

​
Step 3: Verify the Connection

Start a conversation in QoderWork and try calling the service: If QoderWork invokes the MCP server and returns results, you’re all set.

​
FAQ

Q: I added a server but it isn’t working. What should I check? Run through this checklist:
  1. Confirm the JSON config or URL was copied in full and is correctly formatted.
  2. Check your network connection. Some MCP servers require specific network access or VPN.
  3. Verify whether the service needs an extra authorization or login step.
  4. Remove the server from the MCP Servers page and re-add it.
Q: MCP calls feel slow. Is that normal? Response time depends on the service provider. Most calls return within a few seconds. If you’re seeing persistent timeouts, check your network first, then contact the provider.