Personal MCP Remote Agent
by disomanceo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEVICE_ID | No | Unique identifier for this desktop agent. | personal-windows-agent |
| AGENT_TOKEN | Yes | Secret token used to authenticate the desktop agent. Required for security. | |
| DEVICE_NAME | No | Human-readable name for this desktop agent. | Windows Desktop Agent |
| GATEWAY_URL | No | WebSocket URL that the desktop agent connects to. | ws://127.0.0.1:8787/agent |
| GATEWAY_HOST | No | Host interface for the gateway server. | 127.0.0.1 |
| GATEWAY_PORT | No | Port for the gateway server. | 8787 |
| WORKSPACE_ROOT | Yes | Root directory that the agent is allowed to read and run commands in. | |
| PERMISSION_MODE | No | Permission mode for the agent. Only SAFE is currently supported. | SAFE |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/disomanceo/personal-mcp-agent'
If you have feedback or need assistance with the MCP directory API, please join our Discord server