Machine Readiness
Stored receipt and evidence
20
65
0
0
0
Samples
No stored offer samples.
Samples
No stored action samples.
Samples
No stored product samples.
Document
User-Agent: * Allow: / Sitemap: https://xmcp.dev/sitemap.xml
Document
# Docs - [Introduction](/docs): xmcp is a framework for building and shipping MCP servers with TypeScript. Designed with DX in mind, it simplifies setup and removes friction in just one command — making it easy to build & deploy AI tools on top of the Model Context Protocol ecosystem. ## adapters - [Express](/docs/adapters/express): Plug xmcp into your existing Express application. - [NestJS](/docs/adapters/nestjs): Plug xmcp into your existing NestJS application with automatic tool discovery and customizable module configuration. - [Next.js](/docs/adapters/nextjs): Plug xmcp into your existing Next.js application. ## authentication - [API Key](/docs/authentication/api-key): Secure access and protect your MCP server using API keys. - [JSON Web Token](/docs/authentication/jwt): Secure access and protect your MCP server using JSON Web Tokens. - [OAuth](/docs/authentication/oauth): Production-ready OAuth implementations with authentication plugins. ## configuration - [Bundler](/docs/configuration/bundler): Extend the bundler configuration for your MCP server. - [Custom Directories](/docs/configuration/custom-directories): Customize where xmcp looks for tools, prompts, and resources. - [Server Info](/docs/configuration/server-info): Customize the name, description, instructions, icons, and home page of your MCP server. - [Telemetry](/docs/configuration/telemetry): A condensed version of the telemetry policy with actionable opt-out instructions. - [Transports](/docs/configuration/transports): Customize the transport types for your MCP server. ## core-concepts - [CSS](/docs/core-concepts/css): Style your xmcp tools with Tailwind CSS, CSS, or CSS Modules - [External Clients](/docs/core-concepts/external-clients): Learn how to connect to external MCP servers via HTTP or STDIO and generate fully typed TypeScript clients with autocomplete support. - [Middlewares](/docs/core-concepts/middlewares): undefined - [Prompts](/docs/core-concepts/prompts): Prompts are user-controlled instruction templates that enable structured, consistent interactions through parameterized workflows. - [Resources](/docs/core-concepts/resources): Resources are application-driven, read-only data sources that provide context to AI models from files, APIs, databases, and other sources. - [Tools](/docs/core-concepts/tools): Tools are functions that your LLM can actively call and decides when to use based on user requests. They enable AI models to perform actions such as writing to databases, calling external APIs, modifying files, or triggering other logic. ## deployment - [Alpic](/docs/deployment/alpic): Alpic is a MCP-first cloud platform with one-click deployment for xmcp servers. Deploy your xmcp server to Alpic with zero-configuration. - [Cloudflare](/docs/deployment/cloudflare): Cloudflare Workers support in xmcp uses a Cloudflare-native bundle and Wrangler for local dev and deploy. - [Replit](/docs/deployment/replit): Deploy your xmcp application to Replit with a single click. - [Vercel](/docs/deployment/vercel): Vercel supports xmcp with zero-configuration. ## discoverability - [Smithery](/docs/discoverability/smithery): Publish your xmcp server to Smithery for distribution and observability. ## getting-started - [Connecting to your server](/docs/getting-started/connecting): Configure HTTP and STDIO transport connections for local development and production environments - [Installation](/docs/getting-started/installation): Set up your MCP server using automated scaffolding or manual installation, configure build scripts, and troubleshoot transport configurations - [Project structure](/docs/getting-started/project-structure): Explore the file-system based architecture with auto-discovery for tools, prompts, and resources, plus configuration options for custom directory layouts ## guides - [Authentication](/docs/guides/authentication): Secure your MCP server with OAuth 2.1, API keys, or JWT tokens. Understand authentication vs authorization, PKCE, scopes, and token-based access control. Integrate with Better Auth, Clerk, Auth0, or WorkOS. - [Monetization](/docs/guides/monetization): Charge for your MCP tools using license keys or crypto micropayments. Understand human vs agent monetization models, and integrate with Polar or x402. - [xmcp MCP server](/docs/guides/xmcp-mcp-server): Connect coding agents to xmcp's documentation MCP server to get real-time answers about xmcp features, configuration, and best practices. ## integrations - [Auth0](/docs/integrations/auth0): The Auth0 plugin provides authentication for your MCP server using Auth0 with scope-based authorization. - [Better Auth](/docs/integrations/better-auth): Add secure authentication to your MCP server using Better Auth and PostgreSQL - [Clerk](/docs/integrations/clerk): The Clerk plugin provides authentication for your MCP server using Clerk's OAuth system. - [Commet](/docs/integrations/commet): Add subscription-aware billing, feature gating, and usage tracking to your xmcp server with Commet - [Polar](/docs/integrations/polar): Add paywalls and track tool usage with license keys using Polar - [WorkOS](/docs/integrations/workos): The WorkOS plugin provides authentication for your mcp server using WorkOS AuthKit. - [x402](/docs/integrations/x402): The x402 plugin enables tool monetization through the HTTP 402 payment protocol using USDC on Base.
Document
Not stored for this site.