Connect your AI to Agenstry
Drop one config in your AI host and every search, compose, money-flow, similar-agent and market-intelligence skill becomes a callable tool. All snippets render from our live skill catalog, so add a skill on the backend and your AI sees it on next session restart, no template edits, no manifest publish.
Claude Desktop
(MCP host, config file)
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or
%APPDATA%\Claude\claude_desktop_config.json (Windows). Restart Claude Desktop after saving.
All 25 Agenstry tools become available in your conversations.
{
"mcpServers": {
"agenstry": {
"url": "https://agenstry.com/mcp",
"transport": "http"
}
}
}
No API key needed for free skills. For paid skills, top up a Stripe prepaid balance (we’ll debit per call) or pass an x402 x_payment arg in the tool call.
Anthropic Messages API
(claude.ai / claude-sonnet-4.5 + native MCP)Anthropic’s 2025 native MCP connector lets you pass remote MCP servers directly in the request. No server-side SDK on your side. Anthropic does the tool round-trip.
curl https://api.anthropic.com/v1/messages \
-H "x-api-key: $ANTHROPIC_API_KEY" \
-H "anthropic-version: 2023-06-01" \
-H "anthropic-beta: mcp-client-2025-04-04" \
-H "content-type: application/json" \
-d '{
"model": "claude-sonnet-4-5",
"max_tokens": 1024,
"mcp_servers": [{
"type": "url",
"url": "https://agenstry.com/mcp",
"name": "agenstry"
}],
"messages": [{"role": "user", "content": "Use agenstry to find me a hotel-booking A2A agent"}]
}'
Server-side use only. Never bundle ANTHROPIC_API_KEY client-side.
ChatGPT custom GPT (Action)
(plus.openai.com)Create a custom GPT → Configure → Actions → Import from URL and paste our OpenAPI spec. Every paid + free REST skill becomes a callable tool inside that GPT. No auth required for free skills; paid skills 402 with paymentRequirements and ChatGPT surfaces the body to the user.
https://agenstry.com/openapi.json
Paste this URL into the Action importer. We update the spec on every deploy.
Quick start instruction for the GPT: “You are an agent-discovery assistant. Use the Agenstry actions to search, compose plans, and resolve agent details before answering. Show conformance + verified-owner badges in your output.”
Responses API + native MCP
(GA since 2025-05,tools[].type = "mcp")
OpenAI’s Responses API binds remote MCP servers as native tools. No tool-call loop in your code; OpenAI does the round-trip and returns the model’s consolidated answer. Works with gpt-5.x, gpt-4.1, gpt-4o.
from openai import OpenAI
client = OpenAI()
resp = client.responses.create(
model="gpt-5.4-nano",
input="Find me a verified hotel-booking agent on Base. Use compose to rank candidates.",
tools=[{
"type": "mcp",
"server_label": "agenstry",
"server_url": "https://agenstry.com/mcp",
"require_approval": "never"
}]
)
print(resp.output_text)
require_approval can also be "always" per-call or scoped per-tool. See OpenAI’s docs.
Cursor
(Settings → MCP → Add new global MCP server){
"mcpServers": {
"agenstry": {
"url": "https://agenstry.com/mcp"
}
}
}
Cursor reads the same shape as Claude Desktop, so just paste the same block into Cursor’s settings UI.
Cline · Continue · Zed
(every MCP host accepts the same HTTP shape)
These hosts all speak HTTP MCP, so paste the same mcpServers block you used for Claude Desktop into
each one’s settings file. Cline: cline_mcp_settings.json. Continue: config.json
under experimental.modelContextProtocolServers. Zed: ~/.config/zed/settings.json under
experimental.mcp_servers.
agenstry MCP endpoint:
https://agenstry.com/mcp
Transport: HTTP (streamable). No auth on free skills.
n8n · Zapier · Make · plain curl
(no MCP host required, every skill mirrors to REST)
Every skill in the catalog has a REST mirror at /api/v1/skills/<id>. Use an HTTP node in your
automation tool. Same paywall as MCP / A2A: paid skills 402 unless you settle.
# Free skill — no auth
curl https://agenstry.com/api/v1/skills/find_agent?query=hotel%20reservation
# Free deep money-flow snapshot
curl https://agenstry.com/api/v1/skills/money_flows
# Paid skill — settle via x402
curl https://agenstry.com/api/v1/skills/flow_trends \
-H "X-Payment: <base64 x402 v2 payload>"
Full OpenAPI: /api/docs · machine-readable spec: https://agenstry.com/openapi.json
From another A2A agent
(JSON-RPCmessage/send)
We’re a real A2A v1.0 agent. Other agents discover us via our card, call message/send, and
receive a single-shot artifact or stream SSE events. The card declares x402 + AP2 payment extensions so the
caller knows how to settle paid skills.
Agent card: https://agenstry.com/.well-known/agent-card.json
JSON-RPC endpoint: https://agenstry.com/a2a
x402 discovery: https://agenstry.com/.well-known/x402
POST https://agenstry.com/a2a
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": "req-1",
"method": "message/send",
"params": {
"message": {
"role": "user",
"parts": [{"kind": "text", "text": "compose: book a hotel in Amsterdam next weekend"}]
}
}
}
All bundled tools (25)
Auto-rendered from the live app/skill_catalog. Adding a skill on the backend surfaces it here on next
deploy, no template edit needed. Machine-readable: /api/v1/skills.
Why is this all so generic?
Every config you copy points at our stable endpoints: https://agenstry.com/mcp, https://agenstry.com/a2a, https://agenstry.com/openapi.json.
When we add a skill, the agent card / OpenAPI spec / MCP tools-list / well-known/x402 all update automatically because
they read from the same app/skill_catalog.py module. You never have to re-paste this config.
The host detects the new tool on next session start.