Skip to main content
Glama
ajbisht

OpenCodeMode

by ajbisht
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DB_PASSNoPostgreSQL password used in the example postgres connection string.
DB_USERNoPostgreSQL username used in the example postgres connection string.
GITHUB_TOKENNoGitHub token expanded into GITHUB_PERSONAL_ACCESS_TOKEN for the github downstream server.
JIRA_API_TOKENNoJira API token used when configuring the jira downstream server in codemode.config.json.

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
execute_codeA

Execute TypeScript/JavaScript code inside an isolated sandbox to orchestrate tools and filter data. Intermediate data stays in memory; return only the final result to save tokens.

Available APIs on the global mcp object:

/**
 * OpenCodeMode Injected API
 * Every function executes through the secure IPC bridge to the downstream MCP server.
 * Intermediate data stays inside sandbox memory; return only the desired result.
 */
declare namespace mcp {
  namespace demo {
    /**
     * Returns company employees with their department, salary, and performance ratings
     * @param args.department Optional filter by department (e.g. 'Engineering', 'Sales', 'Product')
     */
    function list_employees(args?: {
        department?: string;
      }): Promise<any>;
    /**
     * Awards an annual performance bonus to an employee
     * @param args.employeeId Employee ID (e.g. EMP-01)
     * @param args.amount Bonus amount in USD
     */
    function award_bonus(args: {
        employeeId: string;
        amount: number;
      }): Promise<any>;
  }
}
get_tool_typesA

Returns the complete TypeScript declaration file (.d.ts) describing all available downstream tools.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are clearly distinct: execute_code runs TypeScript/JavaScript in a sandbox, while get_tool_types returns the downstream TypeScript declarations. An agent can easily tell which tool to use for execution versus discovery.

Naming Consistency5/5

Both names follow a consistent snake_case verb_noun pattern: execute_code and get_tool_types. There is no mixing of conventions or vague naming.

Tool Count4/5

Two tools is minimal, but for a meta-execution server this surface is well-scoped: one tool discovers downstream APIs and the other executes code against them. It is slightly thin by typical MCP standards but reasonable for the stated purpose.

Completeness4/5

The pair covers the core lifecycle of discovering downstream tool types and executing orchestration code against them. Minor gaps exist around richer discovery or validation, but the essential workflow has no dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources