Claude Skills now support MCP attachment. This walks adding Scavio's hosted MCP as a search tool inside a custom Skill, so the Skill has live web context without per-task glue code.
Prerequisites
- Claude.ai workspace with Skills enabled
- Scavio API key
- A Skill manifest you control
Walkthrough
Step 1: Define the Skill with MCP attachment in the manifest
Skills support an mcp_servers field.
JSON
{
"name": "market-research",
"description": "Pulls market research from Google/Reddit/YouTube",
"mcp_servers": [
{
"name": "scavio",
"url": "https://mcp.scavio.dev/mcp",
"headers": {"x-api-key": "sk_live_xxx"}
}
]
}Step 2: Reference the named tools in Skill instructions
Tell the Skill which Scavio tools to call when.
Text
# In the Skill description:
# 'Use scavio.search for general SERP. Use scavio.reddit_search for community signal. Use scavio.youtube_search when the user asks about video content.'Step 3: Test the Skill in Claude.ai
Trigger via @market-research or natural invocation.
Text
// In a chat: '@market-research find recent threads about competitor X'Step 4: Monitor tool call traces
Skills surface MCP tool calls in the chat trace.
Text
// Open the trace pane; verify the right Scavio tool fired.
// If wrong tool fires: refine the Skill description with explicit routing rules.Step 5: Bump credit ceiling if needed
500/mo free; $30/mo Project tier for 7K credits.
Text
# Each Scavio tool call = 1 credit. A Skill running 50x/day uses 1.5K credits/mo — within free tier.Python Example
Python
# Skills are configured via the Claude.ai UI / API, not Python. The Scavio side is just the MCP URL.JavaScript Example
JavaScript
// Same — Skills are JSON manifests, no JS needed.Expected Output
JSON
Custom Claude Skill that has live web search, Reddit search, and YouTube search built in via Scavio's MCP. No glue code; the Skill just references the tools by name.