Safe MCP server for twitter_api_safe_relay
Safe MCP server for twitter_api_safe_relay. The twitter api safe relay mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 7 defined tools rather than through you.
A simple MCP server that forwards HTTP requests to twitter_api_safe_relay.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Everything the assistant can do here goes through one of these:
twitter_request_catalog — Searches the latest request catalog by operation name or path and returns executable templatestwitter_api_request — Sends a request to the relay using a templateendpoint — The path sent to the relay. Absolute URLs are not acceptedmethod — GET (default), POST, PUT, PATCH, or DELETEparams — URL query parameters. Object values are converted to JSON stringsbody — JSON request bodyheaders — Optional HTTP headersYou will need 3 environment variables: TWITTER_RELAY_BASE_URL, QUERY_ID, TWITTER_REQUESTS_CATALOG_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Twitter Api Safe Relay MCP's toolset — twitter_request_catalog, twitter_api_request, endpoint and 4 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Twitter Api Safe Relay MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| twitter_request_catalog | Searches the latest request catalog by operation name or path and returns executable templates. |
| twitter_api_request | Sends a request to the relay using a template. |
| endpoint | The path sent to the relay. Absolute URLs are not accepted. |
| method | GET (default), POST, PUT, PATCH, or DELETE. |
| params | URL query parameters. Object values are converted to JSON strings. |
| body | JSON request body. |
| headers | Optional HTTP headers. |
Example MCP client configuration:
```json
{
"mcpServers": {
"twitter-api-safe-relay": {
"command": "npx",
"args": ["twitter_api_safe_relay_mcp"],
"env": {
"TWITTER_RELAY_BASE_URL": "http://localhost:6900"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TWITTER_RELAY_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| QUERY_ID | Configuration value read at startup. | Optional |
| TWITTER_REQUESTS_CATALOG_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.