
Ryter Pro
io.github.apiihub33-cyberPublished by GitHub account apiihub33-cyberv0.1.0Updated Nov 3, 2026
MCP server for humanizing and rewriting text with the Ryter Pro API.
Overview
Local MCP server that lets an assistant humanize or rewrite text through the Ryter Pro API, plus look up basic API configuration info.
- What you can do
- Humanize or rewrite a supplied piece of text using the Ryter Pro API, optionally with a chosen humanizer mode
- Retrieve basic API configuration details and documentation links for the service
- When to use it
- Useful when you want an assistant to rephrase or humanize drafts, articles or other text through a hosted rewriting service rather than doing it purely in-model.
- Requirements
- Runs locally over stdio; requires Python 3.10 or later and the ryterpro-mcp package. A Ryter Pro API key must be supplied in the RYTERPRO_API_KEY environment variable. Optional RYTERPRO_BASE_URL and RYTERPRO_TIMEOUT variables adjust the endpoint and request timeout. Network access to the Ryter Pro API is needed.
Installation
In SourceWeft
- Open Ryter Pro in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Ryter Pro MCP Server
An MCP server that exposes the Ryter Pro text humanizer API as a tool for MCP-compatible clients.
Tools
humanize_text
Humanize or rewrite text with the Ryter Pro API.
Inputs:
text: Text to humanize.mode: Optional humanizer mode supported by your Ryter Pro API.
ryterpro_api_info
Return basic API configuration and documentation links.
Installation
Requires Python 3.10 or later.
Configuration
Set your Ryter Pro API key before running the server:
Optional environment variables:
Run
The server uses the MCP stdio transport by default.
MCP Client Example
For local development from this repository:
Links
License
MIT
Source: README.md at commit 0020d96
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.