FieldPulse Docs
FieldPulse serves a live, anonymous Model Context Protocol server from its documentation host. It is a documentation-retrieval server (search + a read-only virtual filesystem over the docs pages and the OpenAPI specs, plus a feedback submission tool) rather than an executable wrapper around the FieldPulse Open API. The tool list below was retrieved live with an unauthenticated tools/list call, so every inputSchema here is the real published schema, not a reconstruction.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport http
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
Tools
search_field_pulse_docs— Search across the FieldPulse Docs knowledge base to find relevant information, code examples, API references, and guides. Returns contextual content with titles and direct links to documentation pages.query_docs_filesystem_field_pulse_docs— Run a read-only shell-like query (head, cat, rg, tree, ls) against a virtualized in-memory filesystem containing only the FieldPulse documentation pages and OpenAPI specs. This is how a page is read — there is no separate get-page tool.submit_feedback— Report a problem with the documentation site so the docs team can fix it. For documentation content issues only, not product support.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.