Documentation

Inspect the source link, topic match and decision rationale together. Missing metrics are not zero. A decision score is neither a calibrated probability nor a reach guarantee.

Add a public handle to analyze its posts and suggest starter categories and writing style. This does not verify account ownership.

Review the final text before publishing. Editing invalidates earlier approval. If the outcome is unknown, inspect reconciliation evidence before resending. Provider acceptance and a verified remote publication are distinct states.

For normal operation, configure separate session, token-encryption and AI-vault secrets. Keep secrets out of Git. Server, 𝕏 API and AI costs depend on your deployment.

• Setup and worker
• Contribution guide and demo
• Architecture and safety contract
• Implementation status and evidence limits

bun install --frozen-lockfile
bun run dev

Local tests do not establish live 𝕏 grants, email delivery or production publishing.

ispatla.tr provides two connection modes: a local stdio process for a client on your computer, and an HTTP MCP endpoint at /mcp on an ispatla.tr deployment. The remote endpoint uses OAuth authorization and explicit consent. Availability depends on the deployment you use.

Local stdio

Run the repository's MCP host with Bun. It uses the signed-in session cookie supplied to the process; this is a local developer setup, not a public hosted service.

{"mcpServers":{"ispatla":{"command":"bun","args":["run","mcp"],"env":{"ISPATLA_MCP_SESSION_COOKIE":"<session-cookie>"}}}

Keep the local session cookie private. Do not paste it into shared client settings, commit it, or include it in logs.

Remote MCP over OAuth

Configure your client with your ispatla.tr deployment origin plus /mcp. The client discovers OAuth metadata at /.well-known/oauth-authorization-server, registers a redirect URI, then opens a consent page. Use HTTPS for a remote deployment.

https://ispatla.tr/mcp
https://ispatla.tr/.well-known/oauth-authorization-server

Scopes and consent

Available scopes: read, drafts:write, analysis:write, publishing:prepare, receipts:write. Read allows read-only tools. Other scopes allow their named draft, account-analysis, preparation or receipt operations. Review each requested scope before granting access; grants can be revoked in Security settings.

What MCP can and cannot do

Tools are limited to your account and scoped grant. Drafts and publication preparation do not publish a post. A human must review and approve in the ispatla.tr web interface. An agent's confirm parameter is not human consent. MCP results and stored observations do not prove a live provider or production flow was verified.

Evidence limits

Public profile and post data read through FxTwitter are third-party observations, not official confirmation from 𝕏. Treat scores as ispatla.tr calculations and model output as analysis. A provider accepting a request is not proof of a confirmed remote post. This repository inspection does not verify a live production deployment.