About Quillopy MCP
Quillopy MCP is an MCP server published by quillopy in the Developer Tools category: mCP server: Quillopy MCP.
The repository has 123 stars and 7 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/quillopy/quillopy-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Tools (2)
quillopy_chat_with_codeThis tool enables chat with code in a GitHub repository. Only use when explicitly requested by the user. Inform the user that responses may take up to 1 minute to generate.
Parameters not published.
quillopy_searchThis MCP searches and fetches documentation for programming libraries, packages, and frameworks. When a user types @quillopy or @quillopy[documentation_name], they are requesting to use this tool to access programming documentation.
Parameters not published.
Ask AI
Ask AI about Quillopy MCP
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 6 days ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- !License declaredNo license file. Legally you have no right to use it in a product.
- !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
Quillopy MCP — Real Docs. Real Code. Zero Hallucination.
🧠 Your LLM is smart. But it can’t see the latest docs.
❌ Without Quillopy:
- You get code that references functions that were deprecated two years ago
- You spend time debugging things that were never supposed to work
- Answers are vague, outdated, or flat-out wrong
✅ With Quillopy:
Quillopy pipes accurate documentation directly into your code assistant’s context — so it generates real, working, up-to-date code.
No manual uploads. No stale info. No wasted time.
How it works:
- Ask your question in Cursor (or any assistant that supports the MCPs)
- Behind the scenes, Quillopy injects the right docs — automatically
- You get a code completion that actually runs
To explicitly activate Quillopy, just add @quillopy to your question — or use @quillopy[package_name] to specify exactly what library to pull in.
No hacks. No guessing. Just code that works.
Try it with questions like:
“How to code an agent browsing the web to fetch the latest news using browser-use? @quillopy[browser-use]”
“How do I store and retrieve JSON data in Supabase? @quillopy”
“How do I secure routes with the newest NextAuth? @quillopy”
Why devs are switching to Quillopy:
✅ Zero setup — no uploads or config
✅ 600+ libraries pre-indexed and updated in real time
✅ Optimized for minimal context usage (perfect for LLMs)
✅ Works with any library, any version, anytime
🛠️ Getting Started
1. Create an API key
Important: You need a Quillopy API key to use this MCP server. Visit https://quillopy.com to sign up and obtain your API key (free).
2. Install the Quillopy MCP
Option 1: Use Smithery (Recommended)
Smithery provides the easiest way to install and configure the Quillopy MCP across various AI assistant platforms.
# Claude
npx -y @smithery/cli@latest install @quillopy/quillopy-mcp --client claude
# Cursor
npx -y @smithery/cli@latest install @quillopy/quillopy-mcp --client cursor
# Windsurf
npx -y @smithery/cli@latest install @quillopy/quillopy-mcp --client windsurf
For more information and additional integration options, visit https://smithery.ai/server/@quillopy/quillopy-mcp
Option 2: Manual Setup
Cursor
- Navigate to
Settings->Cursor Settings->MCP->+ Add new global MCP server - Copy paste the following config in
~/.cursor/.mcp.json{ "mcpServers": { "quillopy": { "command": "npx", "args": ["-y", "@quillopy/mcp"], "env": { "QUILLOPY_API_KEY": "<your-api-key>" } } } } - Replace
<your-api-key>with your actual API key
Check the Cursor MCP docs for more infos.
Windsurf
Add this to your Windsurf MCP config file. Check the Windsurf MCP docs for more infos.
{
"mcpServers": {
"quillopy": {
"command": "npx",
"args": ["-y", "@quillopy/mcp"],
"env": {
"QUILLOPY_API_KEY": "<your-api-key>"
}
}
}
}
Claude Desktop
Add this to your claude_desktop_config.json.
{
"mcpServers": {
"quillopy": {
"command": "npx",
"args": ["-y", "@quillopy/mcp"],
"env": {
"QUILLOPY_API_KEY": "<your-api-key>"
}
}
}
}
Continue.dev
-
Open your Continue.dev configuration file in either format:
- YAML:
- MacOS/Linux:
~/.continue/config.yaml - Windows:
%USERPROFILE%\.continue\config.yaml
- MacOS/Linux:
- JSON:
- Same location as above, but named
config.json
- Same location as above, but named
- YAML:
-
Add the configuration using either format:
YAML format:
experimental: modelContextProtocolServers: - transport: type: stdio command: node args: ["-y", "@quillopy/mcp"] env: { "QUILLOPY_API_KEY": "<your-api-key>" }JSON format:
{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "stdio", "command": "npx", "args": ["-y", "@quillopy/mcp"], "env": { "QUILLOPY_API_KEY": "<your-api-key>" } } } ] } } -
Save the file - Continue will automatically refresh to apply the new configuration. If the changes don't take effect immediately, try restarting your IDE.
Check Continue MCP docs for more infos.
README fetched from the repository 6 days ago. The original is authoritative.