eXcalibur MCP
Allows monetization with Bitcoin Lightning micropayments, enabling prefunded credit balances and per-tool-call metering.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@eXcalibur MCPPost a tweet: The future of AI + Twitter is here with #eXcalibur MCP 🚀"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
eXcalibur MCP
Sword-swift posting of pretty tweets to X (Twitter) via AI agents, monetized with Bitcoin Lightning micropayments through the DPYC(TM) Tollbooth protocol.
eXcalibur is a FastMCP server that lets AI agents post to X (Twitter) with rich Unicode formatting and optional images. Patron authentication for X uses OAuth2 Authorization Code + PKCE -- no credentials appear in chat. Operator credentials (X app keys, BTCPay) arrive via human-in-the-loop Secure Courier and are stored in the operator's per-operator Neon vault schema. Tool calls are metered with Tollbooth DPYC(TM) pre-funded Lightning balances -- Don't Pester Your Customer.
Part of the DPYC(TM) Social Contract.
Getting Started
Connect via Horizon -- no local install needed:
https://www.fastmcp.cloud/mcp/lonniev/excalibur-mcpStep 1: Check Session
Call excalibur_session_status to see your current session state. If you have
an active session with funded credits, you are ready to post.
Step 2: X OAuth2 + PKCE (Patron Credentials for X)
Get your Nostr npub -- use the dpyc-oracle's
how_to_join()tool, or any Nostr client.Call
excalibur_begin_oauth(npub=<npub>)-- returns anauthorize_url. Open the primaryauthorize_url(not a shortlink) in your browser and authorize the app on X.Call
excalibur_check_oauth_status(npub=<npub>)-- completes the code exchange, vaults the tokens, and activates your session.
Sessions are keyed by npub. Tokens are stored in the Neon vault and auto-refresh on expiry.
Step 3: Secure Courier (Operator Credentials)
Operator credentials (X OAuth2 app keys, BTCPay connection) are delivered via
Secure Courier (service="excalibur-operator"). This is a human-in-the-loop
flow: the operator consciously approves each credential delivery via their
Nostr client. On receive_credentials, the relay DM is destructively drained
-- credentials exist only in the Neon vault after receipt.
Related MCP server: MCP X Server
Credits Model
Tool calls cost api_sats per call. Credits have a tranche_lifetime --
each purchase creates a tranche that expires after the configured lifetime.
Auth and balance tools are always free. Use excalibur_check_balance to see
your balance and tranche expiry. Top up via excalibur_purchase_credits.
Available Tools
Standard Tools (from the wheel)
Standard DPYC(TM) tools are registered by register_standard_tools() from
tollbooth-dpyc. These include
session management, credit operations, Secure Courier, pricing, notarization,
and Oracle delegation. Each tool is identified by a deterministic UUID v5.
Category | Tools |
Session & Billing |
|
Secure Courier |
|
Npub Proof |
|
Purchase |
|
Pricing & Constraints |
|
Notarization |
|
Onboarding |
|
OAuth (X) |
|
Oracle (delegated) |
|
Domain Tools (eXcalibur-specific)
Domain tools are defined in server.py (with storage handlers under
tools/). Prices are set by the operator's pricing model -- preview any
call with check_price. Read and auth tools are free.
Posting to X
Tool | Description |
| Post a text tweet with markdown-to-Unicode rich text formatting |
| Post a tweet with a hero banner image (image URL or SVG rendered to PNG) |
| Fetch the connected X account's handle and name for this patron (free) |
Stored posts (drafts & scheduling)
Tool | Description |
| Store a new post (draft or scheduled); returns its |
| Read one stored post by id (owner-scoped) |
| List your stored posts, server-side sorted, filtered, and paginated |
| Patch a stored post ( |
| Delete a stored post (soft delete by default) |
Snippets & Voice
Tool | Description |
| List your saved post snippets (server-side sorted/filtered/paginated) |
| Read one saved snippet by id |
| Save a reusable snippet (opening/footer/CTA) |
| Delete a saved snippet (free, owner-scoped) |
| Read your saved writing Voice (profile blurb + banned words) |
| Save your per-npub writing Voice |
AI editorial & dynamic blocks
Tool | Description |
| Refine a flagged region of a post with an LLM, server-side |
| Start resolving a dynamic (prompt-backed) post block; returns a claim check |
| Redeem a |
Scheduler
Tool | Description |
| Publish every due scheduled post (operator-only) |
| Read recent scheduler-tick outcomes |
| The scheduler's configuration and current status (free; any proven patron) |
| What the scheduled-post cron Worker is waiting on (operator-only) |
| Run one scheduler tick now (any proven patron) |
| Send the scheduler's proof request again, now (operator-only) |
OAuth flow tools (begin_oauth, check_oauth_status) are now standard tools
provided by the wheel (see the Standard Tools table above).
All tools that take an npub also accept a proof: str parameter for
kind-27235 Schnorr proof attestation.
Security
Npub identity -- Patrons are identified by a Nostr public key (
npub), not an email or password. One keypair per role, managed by the user.Kind-27235 Schnorr proof -- Tool calls carry an NIP-98-style Schnorr signature proving the caller controls the claimed npub. Proof is cached for ~1 hour; renew via
request_npub_proof/receive_npub_proof.Human-in-the-loop Secure Courier -- Credential delivery requires conscious operator approval via Nostr DM. On receipt, the relay message is destructively drained so secrets exist only in the encrypted Neon vault.
Per-operator Neon schema -- Each operator's credentials are stored in an isolated Postgres schema with a dedicated LOGIN role. No cross-operator access.
Architecture
src/excalibur_mcp/
server.py FastMCP server -- domain tools + register_standard_tools()
config.py Pydantic settings from environment variables
oauth_flow.py X-specific OAuth2 Authorization Code + PKCE wrapper
x_client.py X API v2 client with OAuth 2.0 Bearer token auth
formatter.py Markdown -> Unicode rich text (bold, italic, headers)
refine.py Server-side editorial refinement for the post editor
resolve.py Server-side resolution of dynamic (prompt-backed) post blocks
scheduler.py Scheduled-post firing (publishes due posts on the owner's behalf)
tools/ Domain storage handlers (posts, snippets, voices)
db/ eXcalibur persistence on the wheel's NeonVault (posts, scheduler runs, migrations)Key design choices:
OAuth2 Authorization Code + PKCE -- Patron tokens acquired via browser flow.
begin_oauthreturns the primaryauthorize_url(not a shortlink);check_oauth_statuscompletes the exchange. Tokens stored in Neon vault, auto-refreshed on expiry. No OAuth 1.0a.UUID v5 tool identity -- Every tool (standard and domain) has a deterministic UUID derived from its capability name. Pricing, constraints, and billing all key on UUID.
Standard tools from the wheel --
register_standard_tools()provides all DPYC(TM) infrastructure tools. Only domain-specific X/Twitter tools are defined inserver.py.Markdown to Unicode -- Converts
**bold**,*italic*, and# headersto Unicode characters that render in tweets without markup syntax.
Self-Hosting
Environment Variables
DPYC(TM) Identity (required to boot)
Variable | Required | Description |
| Yes | Operator's Nostr secret key for identity bootstrap and DM encryption |
This is the only env var required to start. All other secrets (X app keys, BTCPay credentials) arrive via Secure Courier credential templates and are stored in the per-operator Neon vault schema.
Operator Credentials (via Secure Courier)
These are delivered via Secure Courier (service="excalibur-operator"), not
set as environment variables:
Credential | Description |
| X OAuth2 Client ID (from X Developer Portal) |
| X OAuth2 Client Secret (from X Developer Portal) |
| BTCPay Server URL |
| Store ID for invoices |
| API key with invoice permissions |
Certified operators bootstrap their Neon database URL from the Authority via
encrypted Nostr DM -- NEON_DATABASE_URL is not read from the environment.
Optional Tuning
Variable | Description |
| Comma-separated relay URLs (overrides defaults) |
| Starter credits for new users (default: 0) |
| How long to cache the DPYC community registry (default: 300) |
|
|
| Optional constraint-engine configuration payload |
| Public URL of the scheduled-post cron Worker (default: |
Troubleshooting
Cold start
On first request after deploy, the service may take a few seconds to initialize Neon connections and load the pricing model. The runtime handles this with inline retry -- the caller receives the result after the warm-up completes, not a "service unavailable" error.
Credential lifecycle states
Credential-related responses describe the current lifecycle state with clear guidance, not error messages:
State | Meaning | Next step |
| No npub recognized | Call |
| OAuth flow started, browser not yet authorized | Open the |
| Secure Courier channel opened, credentials not yet received | Reply via Nostr client with credentials JSON |
| Npub proof cache expired (~1 hour) | Call |
| Credits exhausted or tranche expired | Call |
Common tool call situations
"proof is required" -- Call
request_npub_proofthenreceive_npub_proofto prove npub ownership. The cache expires after ~1 hour; renew with a fresh request/receive cycle."Insufficient credit balance" -- Call
purchase_creditsto top up. Check tranche expiry withcheck_balance."Operator credentials not configured" -- Operator setup issue, not the patron's problem.
Don't Pester Your Customer: Do NOT ask the patron to re-authenticate, re-authorize, or re-do OAuth unless the response specifically says the upstream token is expired or invalid.
Development
# Install in development mode
cd excalibur-mcp
python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
# Run tests
.venv/bin/pytest tests/
# Type checking
mypy src/excalibur_mcp/
# Formatting
black src/ tests/
ruff check src/ tests/DPYC(TM) Ecosystem
tollbooth-dpyc -- Python SDK for Tollbooth monetization (vault, auth, pricing, Lightning payments, Nostr identity)
dpyc-community -- Governance registry: membership, advisories, threat model
dpyc-oracle -- Community concierge (free onboarding + member lookup)
tollbooth-authority -- Certification backbone (Schnorr-signed purchase-order certificates)
tollbooth-sample -- Sample Operator (canonical template)
tollbooth-pricing-studio -- iOS pricing-model editor / operator console
cypher-mcp -- Monetized graph answers: named Cypher templates over Neo4j/AuraDB
schwab-mcp -- Charles Schwab brokerage data
thebrain-mcp -- TheBrain personal knowledge graph
excalibur-mcp -- X/Twitter posting
taxsort-mcp -- Tax classification + Cloudflare Pages UI
optionality-mcp -- Options analytics (brokerage-data operator)
tollbooth-oauth2-collector -- OAuth2 callback handler (advocate service)
tollbooth-shortlinks -- URL shortener utility
Trademarks
DPYC, Tollbooth DPYC, and Don't Pester Your Customer are trademarks of Lonnie VanZandt. See the TRADEMARKS.md in the dpyc-community repository for usage guidelines.
License
Apache License 2.0 -- see LICENSE for details.
This server cannot be deployed
Maintenance
Related MCP Connectors
Post, schedule, and track social posts on X, Bluesky, LinkedIn, Instagram and more from AI agents.
X (formerly Twitter) posts, profiles, and search for AI agents. Free key, self-minted, no signup.
Draft, schedule and publish social posts to nine platforms from any AI agent.
Agent registry with Nostr identity, reputation, escrow, observability, and Lightning payments.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with X (Twitter) API v2 for posting tweets, searching, liking, retweeting, and more through natural language.MIT
- AlicenseCqualityDmaintenanceEnables you to write, refine, and publish tweets to X (Twitter) using AI assistance.1Apache 2.0
- AlicenseBqualityDmaintenanceEnables users to interact with X/Twitter via Claude, allowing posting tweets, searching, liking, retweeting, and more using OAuth 2.0 PKCE authentication.107MIT
- FlicenseAqualityCmaintenanceEnables AI assistants to post, search, and manage tweets on X (Twitter) via the MCP protocol.102-