xmcp is a TypeScript framework for building applications with the Model Context Protocol, a standard for connecting AI models with tools and external context. Developers use it to create MCP-based integrations.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add basementstudio/xmcp --skill create-toolgit clone --depth 1 https://github.com/basementstudio/xmcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/basementstudio/xmcp/create-tool)<a href="https://agentmods.dev/skills/basementstudio/xmcp/create-tool"><img src="https://agentmods.dev/badge/skills/basementstudio/xmcp/create-tool/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/basementstudio/xmcp/create-tool"><img src="https://agentmods.dev/badge/skills/basementstudio/xmcp/create-tool.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.00902 |
| Opus 5.5 | $0.00013 | $0.00361 |
| Sonnet 5.5 | $0.00007 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
create-tool scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create xmcp Tool
You are helping the user create a new xmcp tool. Follow this interactive workflow.
Step 1: Gather Information
Before generating any code, ask the user these questions using AskUserQuestion:
-
Tool name (if not provided as argument): What should the tool be named? (Use kebab-case)
-
Handler type: Ask which handler type they need:
- Standard - For data queries, calculations, API calls (returns string/JSON)
- Template Literal (HTML) - For HTML widgets with external scripts
- React Component - For interactive stateful widgets (.tsx file)
-
Schema fields: What parameters should the tool accept? Ask for:
- Parameter name
- Type (string, number, boolean, enum, array, object)
- Description
- Whether it's optional
- Any validation rules
-
Annotations: Ask about behavior hints:
- Is it read-only? (doesn't modify environment)
- Is it destructive? (may delete or modify data)
- Is it idempotent? (repeated calls have same effect)
- Does it interact with external world? (openWorldHint)
-
Widget support (if Template Literal or React): Ask if they need:
- OpenAI tool invocation messages (invoking/invoked status)
- Widget accessibility (widgetAccessible)
- Widget-to-tool communication
Step 2: Generate the Tool
Create the tool file in src/tools/ with the appropriate extension:
.tsfor Standard and Template Literal handlers.tsxfor React Component handlers
File Location
src/tools/{tool-name}.ts # or .tsx for React
Tool Structure Reference
Every xmcp tool has three main exports:
// 1. Schema (optional) - Define parameters with Zod
export const schema = { /* ... */ };
// 2. Metadata (optional) - Tool configuration
export const metadata: ToolMetadata = { /* ... */ };
// 3. Handler (required) - Default export function
export default function handler(params) { /* ... */ }
Quick Reference
Essential Imports
import { z } from "zod";
import { type InferSchema, type ToolMetadata } from "xmcp";
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 118 lines · 33 tokens per session scan A c0c267dac205
create-tool is a skill published in the GitHub repository basementstudio/xmcp (1,342 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 902 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
lookup-agent-run
Find an eve Agent Run from a run ID, project, request reference, or approximate time using authorized evidence available to the consumer.
dashboard-chat-best-practices
Apply dashboard-grade chat UX patterns in the Eve chat template. Use when changing Next.js Cache Components/PPR behavior, static shell layout, Suspense bootstrap boundaries, theme hydration, auth display hydration, signed-in/signed-out static shell behavior, optimistic messages, streaming row identity…
eve-chat-template-eve
Work safely on Eve-specific internals in the Eve chat template. Use when changing the Eve agent, withEve routes, eveChannel auth, useEveAgent, ClientSession/SessionState, persisted event logs, stream/resume behavior, connection authorization, Vercel Connect MCP connections, local Eve tools, or upstream Eve API…
investigate
Investigate a specific issue report with strict, evidence-driven diagnosis.
review
Comprehensive security and correctness audit. Use for review, deep review, thermo nuclear, or thermonuclear requests and branch or PR diff audits.
om-create-opencode-agent
Scaffold a NEW file-defined OpenCode agent for the Open Mercato Agent Orchestrator (the agent assembled from an agents/ / directory of Markdown files and run on the OpenCode runtime / Playground). Creates AGENT.md + OUTCOME.md (+ optional skills/, sub-agents/, tools/), enforces the propose-only hard gates, runs yarn…