jlc-mcp
by InkRoad
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JLC_MCP_HTTP_PORT | No | Loopback HTTP MCP port | 8787 |
| JLC_MCP_EXPORT_DIR | No | Export and rendered-artifact directory | ~/jlc-mcp-exports |
| JLC_MCP_ENABLE_WRITES | No | Enable tools that mutate EasyEDA state | disabled |
| JLC_MCP_WRITE_AUDIT_FILE | No | JSONL write-audit path | user audit directory |
| JLC_MCP_WRITE_PLAN_TTL_MS | No | Lifetime of signed write plans | 2 minutes |
| JLC_MCP_MAX_ARTIFACT_BYTES | No | Maximum artifact size; may only be lowered | 256 MiB |
| JLC_MCP_CREATION_REVERT_TTL_MS | No | Ownership window for created objects | 10 minutes |
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/InkRoad/jlc-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server