Replit MCP Server
# Replit MCP Server
An MCP (Model Context Protocol) server that enables AI assistants to interact with Replit workspaces directly, without needing an agentic browser or constant user intervention.
## Features
- **User Management**: Get current user, lookup users by ID or username
- **Repl Management**: List, create, fork, delete, and get detailed repl information
- **File Operations**: Read, write, create, delete files and directories
- **Environment Variables**: Manage secrets and environment variables
- **Deployments**: Get deployment info and publish repls
- **Search**: Search for content within files
## Installation
### From Smithery
```bash
smithery install replit-workspace --client claude
```
### Manual Installation
1. Clone this repository
2. Install dependencies: `npm install`
3. Build: `npm run build`
4. Run: `npm start`
## Configuration
The server requires a `REPLIT_TOKEN` environment variable containing your Replit `connect.sid` cookie token.
### Getting Your Token
1. Log into Replit in your browser
2. Open Developer Tools (F12)
3. Go to Application > Cookies > replit.com
4. Copy the value of `connect.sid`
### Claude Desktop Configuration
Add to your Claude Desktop config file:
```json
{
"mcpServers": {
"replit": {
"command": "node",
"args": ["/path/to/replit-mcp-server/dist/index.js"],
"env": {
"REPLIT_TOKEN": "your-connect-sid-token"
}
}
}
}
```
## Available Tools (24 Total)
### User Operations
| Tool | Description |
|------|-------------|
| `get_current_user` | Get info about the authenticated user |
| `get_user_by_id` | Get user info by numeric ID |
| `get_user_by_username` | Get user info by username |
### Repl Management
| Tool | Description |
|------|-------------|
| `list_repls` | List repls owned by the user |
| `get_repl_by_url` | Get repl info by URL |
| `get_repl_details` | Get detailed repl info (comments, multiplayers, tags, stats) |
| `set_active_repl` | Set the active repl for subsequent operations |
| `create_repl` | Create a new repl |
| `fork_repl` | Fork an existing repl |
| `delete_repl` | Delete a repl (requires confirmation) |
| `run_repl` | Start a repl |
| `stop_repl` | Stop a running repl |
### File Operations
| Tool | Description |
|------|-------------|
| `read_file` | Read file contents |
| `write_file` | Write content to a file |
| `list_files` | List files in a directory |
| `create_file` | Create a new file |
| `delete_file` | Delete a file |
| `create_directory` | Create a new directory |
| `search_files` | Search for content in files |
### Environment Variables
| Tool | Description |
|------|-------------|
| `get_secrets` | List all environment variables for a repl |
| `set_secret` | Set an environment variable |
| `delete_secret` | Delete an environment variable |
### Deployments
| Tool | Description |
|------|-------------|
| `get_deployment` | Get deployment info for a repl |
| `create_deployment` | Deploy/publish a repl |
## Development
```bash
# Install dependencies
npm install
# Run in development mode
npm run dev
# Build
npm run build
# Start production server
npm start
```
## Deployment to Smithery
1. Ensure you have a `Dockerfile` and `smithery.json` in your repo
2. Push to GitHub
3. Connect your repository via Smithery dashboard
4. Deploy
## API Coverage
This MCP server provides comprehensive coverage of Replit's GraphQL API including:
- User queries and lookups
- Repl CRUD operations
- File system operations
- Environment variable management
- Deployment management
- Search functionality
## License
MIT
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.