mcp-portal
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORTAL_CLI | No | Path to `cursor-agent` / `agent` | |
| MCP_PORTAL_HOME | No | Cache, receipts, evidence (default `~/.cache/mcp-portal`) | |
| MCP_PORTAL_WORKER | No | Overrides the default WSL worker command | |
| MCP_PORTAL_WSL_CD | No | Sets the WSL working directory (default `~`) | |
| MCP_PORTAL_BACKEND | No | Force either local or wsl mode on Windows (`local` or `wsl`) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bulk_readC | Read authorized files and answer a question via Cursor CLI (read-only). |
| code_writeC | Generate code from a spec and reference file; optional server-side write. |
| statusB | Cursor CLI path, auth, cache location, and receipt counters. |
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 3 tools
Each tool serves a clearly distinct purpose: bulk_read is read-only Q&A, code_write generates and optionally writes code, and status reports configuration. There is no overlap in functionality that would cause misselection.
bulk_read and code_write use snake_case but with different modifier patterns (bulk_read is modifier+verb, code_write is noun+verb), while status is a bare noun. The mix makes the convention only partially predictable.
Three tools is within the typical 3-15 range and each earns its place for a focused portal. However, the surface feels slightly thin for a server handling both file reading and code generation.
The domain appears to be Cursor CLI operations for reading and writing code. Core create and read operations exist, but update, delete, and list operations are missing, leaving notable gaps for a full lifecycle.