Docs MCP vs Fmeca
A side-by-side look at the Docs MCP and Fmeca MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
F
FmecaCommunication · Local subprocess (stdio)Deterministic, offline FMECA MCP server: failure modes, criticality matrix, mitigations, readiness56GoodAuth: no auth requiredVerdict: choose Docs MCP for communication work over a hosted endpoint; choose Fmeca for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Docs MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
DOCS_REPO. - You want tools like
search_cometchat_docs, fetch_cometchat_doc_page, get_cometchat_implementation_bundle.
FChoose Fmeca when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
session.open, append, state.get.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | F Fmeca | |
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 84/100 · Excellent | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | DOCS_REPO | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 109 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | 12 |
| Full listing | View Docs MCP | View Fmeca |
Tools & capabilities
Docs MCP tools 4
search_cometchat_docsSearches CometChat documentation including SDK guides (JavaScript, React, iOS, Android, Flutter, React Native), UI Kit references, REST API documentation, integration tutorials, and OpenAPI specs. Returns ranked snippets with titles and direct links to source pages. Pages for the current version of each SDK and UI Kit are preferred over older versions, and each result reports its version label and whether it is current. To reach older docs, pass the `version` filter with that version's label.fetch_cometchat_doc_pageFetches the full content of a single CometChat documentation page by URL or path. Returns the page content as markdown along with title and section metadata. Path can be passed as a full https://www.cometchat.com/docs URL or as a relative path such as '/sdk/javascript/overview'.get_cometchat_implementation_bundleReturns a curated implementation bundle for a named CometChat integration scenario. Each bundle includes prerequisites, install commands, configuration, working code examples, and common pitfalls. Available bundles cover common integration patterns across React, Flutter, iOS, Android, React Native, and the JavaScript SDK.list_cometchat_bundlesLists every available CometChat implementation bundle with its identifier, title, target framework, and last-verified date.
Fmeca tools 12
session.openStart or resume a session; optionally selects the matrix strategy and records analysis metadata (`title`, `level`, `aspect`, `scope_paths`, `parent`), all fixed for the session's life.appendAdd a failure mode (`add_failure_mode`), add a mitigation (`add_mitigation`), or re-score an existing failure mode (`rescore`). `set_mitigation_status` moves a mitigation through planned, implemented, verified or abandoned (verified needs evidence other than a note). `set_failure_mode_disposition`…state.getRead-only projection of the session: every failure mode with its computed criticality, residual, and standing.risk.nextThe highest-criticality unmitigated failure mode — what to address next.readiness.assessThe readiness gate: is every High/Medium residual reduced and every blocker cleared?report.exportThe full FMECA table for the session.scoring.catalogThe fixed observation vocabulary for a strategy — the ids the caller draws from.analyzeStateless one-shot: hand over an entire analysis, get back the entire computed report. No session, no persistence.session.listEvery analysis in the state dir (the project's `.fmeca/` when there is one), with its metadata, standing counts (excluded failure modes are counted separately), `ready`, `ready_verified` and resolution counts. Filters: `level`, `aspect`, `parent`. A log that fails to replay is listed with its error.vetAdvisory: asks Jev (via OpenRouter, needs `OPENROUTER_API_KEY`) whether observations, mitigations, coverage and readiness hold up, and returns probabilities beside the deterministic gate. Never writes or changes a score; without a key it reports `vet_unavailable`.actions.suggestRead-only. Reads a session (or an inline analysis) under a [risk policy](docs/policies.md) and suggests actions: per-failure-mode risk bands, evidence confidence, dispositions, tagged actions and a sign-off verdict. Never changes the analysis or the log.policy.listRead-only. The built-in policy presets and the project's `.fmeca/policies/` files, each with its name, hash and class. A project file that does not load is listed with its `error`.
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.
Docs MCP
{
"mcpServers": {
"cometchat-docs-mcp": {
"url": "https://mcp.cometchat.com/mcp"
}
}
}
Fmeca
{
"mcpServers": {
"fmeca": {
"command": "npx",
"args": [
"-y",
"@matthew-cochran/fmeca"
]
}
}
}
Frequently asked questions
Docs MCP is categorized under Communication and uses a remote HTTP/SSE transport. Fmeca belongs to Communication and uses a local stdio subprocess. Pick Docs MCP for communication work and Fmeca for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Docs MCP is listed as free. Auth: no auth required. Fmeca is listed as free. Auth: no auth required. 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 cometchat-docs-mcp and fmeca as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Docs MCP has a quality signal of 84/100 (Excellent) with 4 views, 0 installs and 109 GitHub stars. Fmeca has 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars.