Poe o3 MCP Server

Created By
Anansitradinga year ago
A lightweight MCP server implementation for accessing OpenAI's o3 model via Poe API
Overview

what is Poe o3 MCP Server?

Poe o3 MCP Server is a lightweight Model Context Protocol (MCP) server implementation that provides access to OpenAI's o3 model and other models via Poe's API, allowing integration of Poe's AI capabilities into MCP-compatible applications.

how to use Poe o3 MCP Server?

To use the server, clone the repository, set up a virtual environment, install dependencies, configure your Poe API key, and run the server using the command python poe_o3_mcp_server.py.

key features of Poe o3 MCP Server?

  • Simple MCP server implementation using FastMCP
  • Direct integration with Poe's API for accessing various models
  • Model selection via command-line style flags in prompts
  • Asynchronous request handling for efficient processing
  • Comprehensive error handling and logging
  • Easy setup and configuration

use cases of Poe o3 MCP Server?

  1. Integrating AI capabilities into custom applications using the o3 model.
  2. Sending queries to different models based on user input.
  3. Testing and developing applications that require AI responses.

FAQ from Poe o3 MCP Server?

  • What is required to run the server?

You need Python 3.8+, a valid Poe API key, and the required dependencies installed.

  • Can I use different models with this server?

Yes! You can select different models by using command-line flags in your prompts.

  • How do I troubleshoot issues?

Check your Poe API key, ensure dependencies are installed, and review server logs for errors.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Anansitrading
Star
0
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago