Skip to content

feat: Add MCP tool support to bazaar extension spec#1134

Open
apmcdermott wants to merge 1 commit intomainfrom
feat/bazaar-mcp-spec
Open

feat: Add MCP tool support to bazaar extension spec#1134
apmcdermott wants to merge 1 commit intomainfrom
feat/bazaar-mcp-spec

Conversation

@apmcdermott
Copy link
Contributor

@apmcdermott apmcdermott commented Feb 9, 2026

Description

Extends the bazaar extension specification to support MCP (Model Context Protocol) tools in addition to HTTP endpoints, enabling resource discovery and cataloging for both endpoint types.

Changes

  • MCP tool support: Added input.type: "mcp" as a discriminated union option alongside input.type: "http"
  • MCP tool structure: Defines fields for MCP tools including tool name, description, inputSchema, and example arguments
  • MCP example: Added complete example showing how to declare an MCP tool endpoint with full schema validation
  • Schema validation: Extended validation requirements to cover MCP tool fields (tool and inputSchema)

Specification Details

The info.input object now supports a discriminated union:

  • input.type: "http" — HTTP endpoints (GET, HEAD, DELETE, POST, PUT, PATCH)
  • input.type: "mcp" — MCP tools with tool name, input schema, and example arguments

MCP tools use the same discovery pattern as HTTP endpoints, allowing facilitators to catalog and index both endpoint types in a unified discovery service.

Checklist

  • I have formatted and linted my code
  • All new and existing tests pass
  • My commits are signed (required for merge) -- you may need to rebase if you initially pushed unsigned commits
  • I added a changelog fragment for user-facing changes (docs-only changes can skip)

@cb-heimdall
Copy link

cb-heimdall commented Feb 9, 2026

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

@vercel
Copy link

vercel bot commented Feb 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
x402 Ready Ready Preview, Comment Feb 9, 2026 3:54pm

Request Review

@github-actions github-actions bot added the specs Spec changes or additions label Feb 9, 2026
Add documentation for cataloging MCP tools alongside HTTP endpoints.
MCP tools use a simpler structure with just tool name and inputSchema,
without the method/body/queryParams split needed for HTTP.
@apmcdermott apmcdermott marked this pull request as ready for review February 9, 2026 15:58
@apmcdermott apmcdermott changed the title feat(bazaar): Add MCP tool support to discovery extension spec feat: Add MCP tool support to bazaar extension spec Feb 9, 2026
## Summary

The `bazaar` extension enables **resource discovery and cataloging** for x402-enabled endpoints. Resource servers declare their endpoint specifications (HTTP method, input parameters, and output format) so that facilitators can catalog and index them in a discovery service.
The `bazaar` extension enables **resource discovery and cataloging** for x402-enabled endpoints and tools. Resource servers declare their endpoint specifications (HTTP method or MCP tool name, input parameters, and output format) so that facilitators can catalog and index them in a discovery service.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I'd say and MCP tools, as it's the first line of the summary before MCP has been brought up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

specs Spec changes or additions

Development

Successfully merging this pull request may close these issues.

3 participants