Inclusio MCP vs .prompts
A side-by-side look at the Inclusio MCP and .prompts MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
I
Inclusio MCPDeveloper ToolsInclusio MCP server for accessibility-first LaTeX publishing (PDF/UA-2, WTPDF, PDF/A-4f).47FairAuth: no auth required.
.promptsDeveloper Tools.prompts, the home to all your AI prompts, everywhere you need them.38FairAuth: not declaredVerdict: choose Inclusio MCP for developer tools work; choose .prompts for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
IChoose Inclusio MCP when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
- You have the keys it needs:
INCLUSIO_CONTENT_DIR. - You want tools like
list_docs, doc_count, render.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | I Inclusio MCP | . .prompts |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 47/100 · Fair | 38/100 · Fair |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | INCLUSIO_CONTENT_DIR | None listed |
| Verified owner |
Tools & capabilities
Inclusio MCP tools 4
list_docsEnumerate documents registered in the content treedoc_countQuick count of available documentsrenderBuild a tagged, conformant PDF (and other formats) for a documentaudit_pdfAccessibility audit of a PDF (veraPDF)
.prompts tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Inclusio MCP
No confirmed install command for Inclusio MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
.prompts
No confirmed install command for .prompts yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Inclusio MCP is categorized under Developer Tools and uses an install path we have not confirmed yet. .prompts belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Inclusio MCP for developer tools work and .prompts for developer tools.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Inclusio MCP is listed as free. Auth: no auth required. .prompts has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add inclusio-mcp and prompts as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Inclusio MCP has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. .prompts has 38/100 (Fair) with 5 views, 0 installs and 0 GitHub stars.