MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

PraisonAI

Earlier Revision Confidence: High (0.90)

PraisonAI is an MCP client published by Mervin Praison, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-09-15.

Does PraisonAI support the current MCP specification (2026-07-28)?

Not yet confirmed. PraisonAI is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-09-15.

Which MCP client features does PraisonAI support?

PraisonAI supports: tools (last verified 2026-09-15).

Does PraisonAI support MCP revision 2025-11-25?

Yes. PraisonAI supports MCP revision 2025-11-25 (checked 2026-09-15).

When were PraisonAI's facts last verified?

2026-09-15. Each fact on this page links to the sources used to verify it.

PraisonAI is a Python multi-agent framework whose praisonaiagents[mcp] package (installed with pip install "praisonaiagents[mcp]") provides the MCP() client class that connects agents to external MCP servers. The class auto-detects transport from the server address: a bare command string spawns a local stdio subprocess, an http(s):// URL uses Streamable HTTP with auth via custom headers, a ws:// or wss:// URL uses WebSocket with an auth_token parameter, and a URL ending in /sse uses legacy SSE. Since PR #4423 (merged 2026-08-26), the client raises rather than silently continuing when a stdio server times out, errors during initialization, or advertises zero tools. The client is one of three MCP roles documented across the PraisonAI packages, alongside a light server (praisonai-code) and a heavy-host server (praisonai-mcp), each published separately on PyPI.

PraisonAI's transports documentation carries an explicit page-level statement, "Protocol Revision: 2025-11-25", on the client transports page. Because that statement names a specific past revision rather than the current one, spec_status is recorded as legacy with 2025-11-25 as the latest verified revision; the client's own docs separately describe legacy SSE support as tied to "Protocol version 2024-11-05" for that specific transport. No page fetched this session makes an equivalent statement for the praisonai-mcp server package, so this revision claim covers the client role only.

Which MCP spec revisions does PraisonAI support?

Spec revision Status Last checked Evidence
MCP 2025-11-25 Supported Source

How was this verified, and what are the sources?

Verified · method: vendor-docs · confidence 0.90 (High).

  1. praison.ai/docs/mcp/transports.md, fetched 2026-09-15 - "Protocol Revision: 2025-11-25" callout; "PraisonAI Agents supports all MCP transport mechanisms for connecting to MCP servers"; documents stdio ("NPX packages, Python scripts"), Streamable HTTP (auto-detected from URL, auth via custom headers), WebSocket (ws:// or wss://, with auth_token=), and "SSE (Legacy)" (URLs ending in /sse, "Protocol version 2024-11-05") - accessed
  2. praison.ai/docs/features/mcp.md, fetched 2026-09-15 - "MCP (Model Context Protocol) lets agents connect to external tool servers, instantly adding file system access, database queries, API integrations, and more"; names praisonaiagents[mcp] as the client package (distinct from the light-server praisonai-code and heavy-host praisonai-mcp packages); notes MCP() now raises on stdio timeout, init error, or zero advertised tools (PR #4423, merged 2026-08-26) - accessed
  3. praison.ai/docs/features/mcp-three-layers.md, fetched 2026-09-15 - table naming the client layer "praisonaiagents/mcp/", installed via pip install "praisonaiagents[mcp]", role "Connect agents to external MCP servers" - accessed
  4. PyPI praisonaiagents package metadata, fetched 2026-09-15 - version 1.7.6, latest upload 2026-09-14T17:11:19Z (sdist) - accessed
  5. PyPI praisonai package metadata, fetched 2026-09-15 - info.name "PraisonAI", version 4.7.8, latest upload 2026-09-14T17:13:10Z - accessed