Replit MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REPLIT_TOKEN | Yes | Your Replit connect.sid cookie token. Log into Replit in your browser, open Developer Tools (F12), go to Application > Cookies > replit.com, and copy the value of connect.sid |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_userB | Get information about the currently authenticated Replit user |
| list_replsC | List repls owned by the current user |
| get_repl_by_urlC | Get information about a repl by its URL |
| set_active_replC | Set the active repl ID for subsequent file operations |
| read_fileC | Read the contents of a file in a Replit workspace |
| write_fileC | Write content to a file in a Replit workspace |
| list_filesC | List files and directories in a Replit workspace |
| create_fileC | Create a new file in a Replit workspace |
| delete_fileC | Delete a file from a Replit workspace |
| create_directoryC | Create a new directory in a Replit workspace |
| run_replC | Start/run a Replit workspace |
| stop_replB | Stop a running Replit workspace |
| search_filesC | Search for content within files in a Replit workspace |
| get_user_by_idC | Fetch user information by their numeric ID |
| get_user_by_usernameC | Fetch user information by their username |
| create_replC | Create a new repl |
| fork_replC | Fork an existing repl by URL |
| delete_replB | Delete a repl by ID (requires confirmation) |
| get_secretsC | List all environment variables/secrets for a repl |
| set_secretC | Set an environment variable/secret for a repl |
| delete_secretC | Delete an environment variable/secret from a repl |
| get_deploymentB | Get deployment information for a repl |
| create_deploymentC | Deploy/publish a repl |
| get_repl_detailsC | Get detailed repl information including comments, multiplayers, tags, run count, like count, and fork count |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Each tool has a clearly distinct purpose targeting specific resources and actions, such as create_repl vs. fork_repl for different creation methods, and get_repl_by_url vs. get_repl_details for different information retrieval levels. There is no significant overlap that would cause confusion in tool selection.
All tool names follow a consistent verb_noun pattern with snake_case, such as create_deployment, delete_file, and get_current_user. This uniformity makes the tool set predictable and easy to understand across all 24 tools.
With 24 tools, the count is on the higher side but still within a reasonable range for a comprehensive Replit management server. It covers many operations, though it might feel slightly heavy compared to more focused servers.
The tool set provides complete CRUD and lifecycle coverage for Replit resources, including repls, files, deployments, secrets, and users. There are no obvious gaps, and agents can perform all essential operations without dead ends.