Where it fits
Support teams that want an assistant to read and answer Teletype conversations.
- Read customer conversations.
- Manage contacts.
- Send replies across channels.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with Teletype
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Ask which skill or flow fits a situation. It routes among the user-invoked skills in this repository.
Interview the user about a plan or design until its assumptions and trade-offs are clear.
Question a plan or decision until its weak points and missing details are clear.
No skills found
Try a different search term or clear the filters.
Install the Teletype stdio server
The provider's OpenCode config uses a local stdio server with TELETYPE_API_TOKEN in the environment, protocol auto and codemode false. The hosted endpoint is an HTTP alternative for clients that support remote MCP.
- Create a Public API token
Create a Teletype Public API token and set TELETYPE_API_TOKEN in the client environment.
- Add the local server in OpenCode
Use the provider's local stdio shape rather than the remote URL.
{"mcp":{"servers":{"teletype":{"type":"local","command":["npx","-y","teletype-mcp-server","--stdio"],"environment":{"TELETYPE_API_TOKEN":"{env:TELETYPE_API_TOKEN}"},"protocol":"auto","codemode":false}}}}
Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
The installer uses the server name teletype. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
teletypeappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Read customer conversations. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
- The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
Teletype documentationhttps://github.com/Teletype-App/teletype-mcp-server/blob/HEAD/docs/CLIENTS.md#cursorGitHub repositoryhttps://github.com/Teletype-App/teletype-mcp-server