Search Results for "docs"

This repository aggregates a large set of specialized subagents and slash commands designed for Claude Code, giving developers domain-focused “teammates” they can summon on demand. Each subagent is defined by a concise role, tools, and behaviors, and ships as Markdown you can drop into your .claude/agents/ directory. The collection targets common developer workflows such as scaffolding, refactoring, test writing, documentation, security checks, and project management. It includes a CLI...

n8n-mcp is a Model Context Protocol (MCP) server that turns the n8n workflow platform into a set of first-class, typed tools an AI assistant can understand and operate. It exposes structured knowledge of n8n nodes and operations so an agent can reason about workflows, parameters, and executions without scraping docs or guessing API shapes. The server focuses on making Claude Desktop (and other MCP-capable clients) “n8n-literate,” enabling tasks such as inspecting existing workflows, proposing node chains, and validating configuration before runs. It ships with organized resources and tool definitions that map cleanly to n8n’s ecosystem, improving reliability compared with ad-hoc prompt patterns. ...

MetaMCP is an all-in-one MCP aggregator, orchestrator, and middleware that merges many MCP servers into a single, policy-aware server you can point any MCP client at. It’s built to centralize discovery, apply middlewares (e.g., auth, rate limits, transforms), and present a unified catalog of tools and resources from diverse backends. The repository and site describe it as “the one MCP to manage all your MCPs,” with diagrams and examples showing how to compose fleets behind a single endpoint....

...It ships with a web/GUI experience and works smoothly inside MCP-capable IDEs, making it useful as both a personal organizer and a programmable task substrate for software projects. Stars, registry listings, and docs point to active usage across the MCP community. The result is a practical “task brain” that agents can query and evolve over time.

...The server speaks directly to your app over its ASGI interface, avoiding extra HTTP hops between the MCP layer and your API, which reduces latency and simplifies deployment. A tiny bootstrap is enough to stand up an MCP server and, if desired, mount an HTTP transport for remote clients. The docs emphasize a FastAPI-first workflow: keep your schemas, reuse your middleware, and surface endpoints to agents without rewriting controllers. The project is active, with examples and a dedicated site that shows getting started, security, and transport options.