"Developing an application by analyzing specified development and API documentation" matching MCP servers:

A comprehensive MCP server with RESTful API that enables file operations, command execution, project management, and AI integration for remote development control with security features and real-time communication.

Provides unrestricted access to your development environment with filesystem operations and shell command execution capabilities, including sudo support for local development machines.

MCP server for the Stashcat messenger API. Enables AI assistants to read and send messages, manage channels, conversations, files, polls, and more.

Enables AI clients to read, write, search, and manage files in an Obsidian vault via MCP over SSE, running standalone without the Obsidian desktop app.

MCP server that provides file operations and Moonshot API-powered tools (reasoning, code review, testing, research, web search, agent) for Kimi K2.5, requiring only a Moonshot API key.

Enables conversion between PDF/Office documents and structured JSON, supporting extraction and generation of document content.

Enables AI assistants to interact with PDF documentation files stored locally. Provides tools to list, read, search, and extract metadata from CRM API documentation PDFs through natural language queries.

Works out a health plan from your own record: which screening is due and evidence-based suggestions with citations. Reads and writes one health-roadmap.json file on your machine; nothing is sent to a server.

A bridge server that allows LLM tools to interact with an Obsidian vault through a local REST API, enabling file operations, note management, and metadata access through natural language.

Enables AI assistants to inspect Ignition gateway backups, project exports and tag exports locally and turn them into an editable engineering reference and manual pack workspace. Runs over stdio so agents can explain, validate and complete the evidence-traced documents without uploading anything.

A local MCP server for Claude Desktop with persistent task management, file operations, document generation, and PDF indexing.

Enables AI agents to read, create, update and delete any file in a mounted folder of markdown notes, patch individual headings, blocks or frontmatter keys, search by text or JsonLogic queries over frontmatter, tags and links, and stream note changes as events. Runs as a standalone container requiring no Obsidian installation and binds only to private networks such as Tailscale or WireGuard.

An MCP server that gives LLM clients access to a SQL Server database and the local filesystem, including file operations and image handling.

Enables document conversion between PDF, DOCX, and Markdown formats to facilitate reading and editing complex files in AI tools like Claude Desktop or Cursor. It utilizes marker-pdf and pandoc to provide structured text versions of documents, helping to manage context and support unsupported file types.

Mac file and terminal tools for local AI clients, plus an opt-in ChatGPT Developer Mode relay. Checked edits, bounded reads and real exit codes. Free MIT agent; OpenAI listing under review. Owner-level access, not a sandbox.

A Model Context Protocol (MCP) server for ZeroDrive file management. It enables AI assistants like Claude to interact with ZeroDrive cloud storage through a standardized interface.

Enables AI clients to securely execute remote commands and transfer files over SSH through standardized MCP tools, with multi-host management, flexible authentication, and an admin console.

MCP server for creating and reading Word (.docx) documents with rich formatting support.

A security-first MCP server that provides LLMs with structured tools for filesystem, process, search, build/test/lint, IDE integration, and more.

TheWeave is a markdown-native memory architecture for Claude and any MCP-aware agent. Your agent's memory lives as plain .md files you own: a 5-verb MCP core over the vault, query-driven PageRank retrieval, bi-temporal facts (valid_from / valid_until), and a persona-as-vault model. No database and no embeddings server. The files are the memory, inspectable in your editor and versionable in git.