Skip to main content
Glama
myshell-joe

Shellagent MCP Server

by myshell-joe
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

shellagent-mcp MCP Server

NPM Downloads

A Model Context Protocol (MCP) server for shellagent-mcp

Requirements

  • Node.js 18 or newer

  • VS Code, Cursor, Windsurf, Claude Desktop or any other MCP client

Getting started

Local (Stdio)

First, install the Commands MCP server with your client. A typical configuration looks like this:

{
  "mcpServers": {
    "shellagent-mcp": {
      "command": "npx",
      "args": [
        "mcp-server-shellagent-mcp@latest"
      ]
    }
  }
}

You can also install the shellagent-mcp MCP server using the VS Code CLI:

# For VS Code
code --add-mcp '{"name":"shellagent-mcp","command":"npx","args":["mcp-server-shellagent-mcp@latest"]}'

After installation, the Commands MCP server will be available for use with your GitHub Copilot agent in VS Code.

Go to Cursor Settings -> MCP -> Add new MCP Server. Name to your liking, npx mcp-server-shellagent-mcp. You can also verify config or add command like arguments via clicking Edit.

{
  "mcpServers": {
    "shellagent-mcp": {
      "command": "npx",
      "args": [
        "mcp-server-shellagent-mcp@latest"
      ]
    }
  }
}

Follow Windsuff MCP documentation. Use following configuration:

{
  "mcpServers": {
    "shellagent-mcp": {
      "command": "npx",
      "args": [
        "mcp-server-shellagent-mcp@latest"
      ]
    }
  }
}

Follow the MCP install guide, use following configuration:

{
  "mcpServers": {
    "shellagent-mcp": {
      "command": "npx",
      "args": [
        "mcp-server-shellagent-mcp@latest"
      ]
    }
  }
}

Remote (SSE / Streamable HTTP)

At the same time, use --port $your_port arg to start the browser mcp can be converted into SSE and Streamable HTTP Server.

# normal run remote mcp server
npx mcp-server-shellagent-mcp --port 8089

You can use one of the two MCP Server remote endpoint:

  • Streamable HTTP(Recommended): http://127.0.0.1::8089/mcp

  • SSE: http://127.0.0.1::8089/sse

And then in MCP client config, set the url to the SSE endpoint:

{
  "mcpServers": {
    "shellagent-mcp": {
      "url": "http://127.0.0.1::8089/sse"
    }
  }
}

url to the Streamable HTTP:

{
  "mcpServers": {
    "shellagent-mcp": {
      "type": "streamable-http", // If there is MCP Client support
      "url": "http://127.0.0.1::8089/mcp"
    }
  }
}

In-memory call

If your MCP Client is developed based on JavaScript / TypeScript, you can directly use in-process calls to avoid requiring your users to install the command-line interface to use Commands MCP.

import { Client } from '@modelcontextprotocol/sdk/client/index.js';
import { InMemoryTransport } from '@modelcontextprotocol/sdk/inMemory.js';

// type: module project usage
import { createServer } from 'mcp-server-shellagent-mcp';
// commonjs project usage
// const { createServer } = await import('@agent-infra/mcp-server-commands')

const client = new Client(
  {
    name: 'test commands client',
    version: '1.0',
  },
  {
    capabilities: {},
  },
);

const server = createServer();
const [clientTransport, serverTransport] = InMemoryTransport.createLinkedPair();

await Promise.all([
  client.connect(clientTransport),
  server.connect(serverTransport),
]);

// list tools
const result = await client.listTools();
console.log(result);

// call tool
const toolResult = await client.callTool({
  name: 'test_tool',
  arguments: {
    hello: 'hello'
  },
});
console.log(toolResult);

Developement

Access http://127.0.0.1:6274/:

npm run dev

Available Tools

1 tool
get_app_infoC

Get application information using app_id

ParametersJSON Schema
NameRequiredDescriptionDefault
app_idYesThe ID of the application to fetch information for

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states the basic action ('Get application information') without adding any context about permissions, rate limits, error handling, or what the returned information includes. This leaves significant gaps in understanding how the tool behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise and front-loaded: 'Get application information using app_id'. It's a single sentence with no wasted words, efficiently conveying the core purpose and parameter usage. This makes it easy to parse and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and no output schema, the description is incomplete. It doesn't explain what 'application information' includes, how errors are handled, or any behavioral traits. For a tool with no structured data beyond the input schema, the description should provide more context to be fully helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the parameter 'app_id' fully documented. The description mentions 'using app_id', which aligns with the schema but doesn't add any extra meaning beyond what's already provided. According to the rules, with high schema coverage, the baseline is 3 when no additional parameter info is given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get application information using app_id'. It specifies the verb ('Get') and resource ('application information'), making it easy to understand what the tool does. However, since there are no sibling tools, it doesn't need to differentiate from alternatives, which is why it doesn't reach a perfect score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It simply states what the tool does without mentioning any context, prerequisites, or exclusions. There are no sibling tools, so no differentiation is needed, but it still lacks any usage instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedget_app_info
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3/5.0
Disambiguation5/5

With only one tool, there is no possibility for confusion or overlap between tools. The tool 'get_app_info' has a clear, singular purpose that cannot be misselected against other tools.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'get_app_info' follows a clear verb_noun pattern, and there are no other tools to compare it against for inconsistency.

Tool Count2/5

A single tool is too few for a server named 'Shellagent MCP Server', which suggests a broader scope related to shell operations or agent management. This minimal toolset feels thin and incomplete for such a domain, limiting functionality significantly.

Completeness1/5

The tool surface is severely incomplete. For a shell agent server, obvious gaps include basic operations like executing commands, listing processes, managing files, or interacting with the system. The single tool 'get_app_info' does not cover the expected domain at all, leading to dead ends for agents.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

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/myshell-joe/Shellagent-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server