Adding WebMCP to Your Site
This guide covers how to add WebMCP support to your website so users can connect it to WebMCP Master and interact with it through AI.
Overview
Adding WebMCP to your site involves three steps:
- Publish a manifest — a JSON file describing your site and its tools
- Implement tool endpoints — API endpoints that handle tool calls
- Set up authentication — how the platform authenticates requests
WordPress
Install the Plugin
- Download the WebMCP plugin from the WordPress plugin directory or upload it manually.
- Go to wp-admin > Plugins > Add New > Upload Plugin.
- Install and activate the plugin.
Configure
- Go to wp-admin > Settings > WebMCP.
- The plugin auto-generates a manifest based on your site's content types.
- Review the available tools (e.g.,
search_posts,get_post,create_post,list_categories). - Configure authentication — the plugin supports Bearer token and OAuth.
- Save settings.
Generated Manifest
The plugin publishes the manifest at /.well-known/webmcp.json automatically. It includes tools for:
- Searching and reading posts, pages, and comments
- Creating and editing content (with appropriate permissions)
- Managing categories and tags
- User information (read-only)
XenForo
Install the Addon
- Download the AI Connect addon for XenForo.
- Upload it to your XenForo installation via the admin panel.
- Go to Admin > Add-ons and install it.
Configure
- Go to Admin > AI Connect > Settings.
- Configure which forum features to expose as tools.
- Set up authentication (Bearer token per user, or OAuth).
- The manifest is published at
/.well-known/webmcp.json.
Available Tools
search_threads— search forum threads by keyword, date, categoryget_thread— retrieve a thread with its postscreate_post— reply to a threadget_user— look up user profile informationlist_categories— list forum categories
Drupal
Install the Module
- Install the WebMCP Drupal module via Composer or manual upload.
- Enable it in Admin > Extend.
- Configure at Admin > Configuration > WebMCP.
Configure
The module supports:
- Content type mapping — which Drupal content types become tools
- Permission mapping — which Drupal roles authorize which tools
- OAuth integration via Drupal's built-in OAuth module
Custom Implementation
For any website or application, implement the WebMCP protocol directly:
Step 1: Create the Manifest
Create a JSON file and serve it at /.well-known/webmcp.json:
json
{
"name": "My Application",
"version": "1.0.0",
"description": "Project management tool",
"server": {
"url": "https://myapp.example.com/api/webmcp"
},
"auth": {
"type": "bearer"
},
"tools": [
{
"name": "search_tasks",
"description": "Search for tasks by keyword and status",
"input_schema": {
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Search keyword"
},
"status": {
"type": "string",
"enum": ["open", "in_progress", "done"],
"description": "Filter by task status"
}
},
"required": ["query"]
}
}
]
}Step 2: Implement Tool Endpoints
Create an API endpoint that handles tool call requests:
POST /api/webmcp/tools/{tool_name}
Authorization: Bearer <user-token>
Content-Type: application/json
{
"query": "login bug",
"status": "open"
}Your endpoint should:
- Validate the Bearer token
- Parse the input parameters
- Execute the operation
- Return a JSON result
json
{
"results": [
{
"id": 42,
"title": "Login page shows error on mobile",
"status": "open",
"assignee": "jane",
"created": "2026-05-10"
}
]
}Step 3: Set Up Authentication
For Bearer token authentication:
- Generate API tokens per user in your application
- Validate the token on every incoming request
- Return 401 for invalid tokens
For OAuth (recommended for production):
- Implement OAuth 2.0 with PKCE
- See the Authentication guide for the full flow
Testing Your Integration
After setting up:
- Visit
https://yoursite.com/.well-known/webmcp.jsonin a browser — verify the manifest loads correctly - Add your site in WebMCP Master's vault — the platform should discover the manifest and list the tools
- Start a chat with your site selected — ask the AI to use one of your tools
- Check your server logs — verify the tool call arrived with proper authentication
Checklist
- [ ] Manifest served at
/.well-known/webmcp.jsonover HTTPS - [ ] All tools defined with name, description, and input_schema
- [ ] Authentication configured (Bearer or OAuth)
- [ ] Tool endpoints return valid JSON
- [ ] Error responses include meaningful messages
- [ ] Rate limiting implemented on tool endpoints
- [ ] CORS headers set if needed (typically not needed since the platform calls server-side)