MCP (Model Context Protocol) integration for Friday Framework
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"friday-framework-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Friday MCP MCP tools clients, transports and programmatic servers. Use the protocol APIs directly or let Friday Runtime own discovery, tool admission, diagnostics and lifecycle. **Distribution:** [friday-framework-mcp](https://pypi.org/project/friday-framework-mcp/) · **Import:** `friday_mcp` **Python:** 3.13.4+ · **Status:** alpha · **License:** MIT ## Installation ```bash python -m pip install "friday-framework-mcp==0.1.0a4" ``` Friday distributions use the same release version; keep internal Friday dependencies aligned. ## Quick start: a local tools server and client These two files use installed packages and an owned local subprocess. They require no network, credentials or model. Save this as `server.py`: ```python import asyncio from friday_mcp.client.protocol import JSONValue from friday_mcp.server import ModernStdioMCPServer, ToolCallResult server = ModernStdioMCPServer() async def echo(arguments: dict[str, JSONValue]) -> ToolCallResult: return ToolCallResult.text(str(arguments["message"])) server.register_tool( { "name": "echo", "description": "Echo a message", "inputSchema": { "type": "object", "properties": {"message": {"type": "string"}}, "required": ["message"], "additionalProperties": False, }, }, echo, ) asyncio.run(server.serve()) ``` Save this beside it as `client.py`, then run `python client.py`: ```python import asyncio from pathlib import Path import sys from friday_mcp.client.stdio import StdioMCPClient async def main() -> None: async with StdioMCPClient( name="demo", command=sys.executable, args=["-u", str(Path(__file__).with_name("server.py"))], protocol_profile="modern", ) as client: await client.list_tools() print(await client.call_tool("echo", {"message": "Hello from MCP"})) asyncio.run(main()) ``` Expected output: `Hello from MCP`. Keep server stdout exclusively for protocol messages. Always await client/serve…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.