Skip to main content
Glama
itsocialist

Claude Code Connector MCP

by itsocialist

list_projects

Retrieve all registered projects with their current status to manage development workflows across Claude interfaces.

Instructions

List all registered projects with status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeInactiveNoInclude inactive projects

Implementation Reference

  • The core handler function that executes the list_projects tool logic: instantiates ProjectManager, fetches all projects, optionally filters inactive ones, maps to simplified output format including id, name, rootPath, active, lastAccessed, and hasClaudeState.
    export async function listProjects(args: ListProjectsArgs): Promise<{
        projects: any[]; // Returning simplified project objects
    }> {
        const projectManager = new ProjectManager();
        const allProjects = await projectManager.getAllProjects();
    
        let projects = allProjects;
    
        // Filter inactive projects unless requested
        if (!args.includeInactive) {
            projects = projects.filter(p => p.active);
        }
    
        // Map to output format
        return {
            projects: projects.map(p => ({
                id: p.id,
                name: p.name,
                rootPath: p.rootPath,
                active: p.active,
                lastAccessed: p.lastAccessed,
                hasClaudeState: true // TODO: check actual state file existence
            }))
        };
    }
  • TypeScript interface defining the input schema for the list_projects tool, with optional includeInactive boolean flag.
     */
    export interface ListProjectsArgs {
      includeInactive?: boolean;
    }
  • src/index.ts:70-79 (registration)
    Tool registration in the ListToolsRequestHandler, defining the name, description, and inputSchema for list_projects.
    {
      name: 'list_projects',
      description: 'List all registered projects with status',
      inputSchema: {
        type: 'object',
        properties: {
          includeInactive: { type: 'boolean', description: 'Include inactive projects' }
        }
      }
    },
  • src/index.ts:125-128 (registration)
    Dispatch case in the CallToolRequestHandler switch statement that invokes the listProjects handler function.
    case 'list_projects':
      return {
        content: [{ type: 'text', text: JSON.stringify(await listProjects(args as unknown as ListProjectsArgs), null, 2) }]
      };
  • src/index.ts:28-28 (registration)
    Import statement for the listProjects handler function.
    import { listProjects } from './tools/list_projects.js';
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. It states it lists projects 'with status', hinting at behavioral output, but doesn't disclose key traits like pagination, sorting, default behavior (e.g., active-only unless specified), authentication needs, or rate limits. For a list tool with zero annotation coverage, this is inadequate.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word contributes directly to the purpose without redundancy.

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 no annotations and no output schema, the description is incomplete for a list tool. It lacks details on return format (e.g., structure of projects, what 'status' entails), behavioral constraints, or error handling. With low complexity but missing output info, it should provide more context for effective use.

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?

Schema description coverage is 100%, with one parameter ('includeInactive') fully documented in the schema. The description adds no parameter-specific information beyond implying status inclusion, which the schema already covers. Baseline 3 is appropriate as the schema handles parameter semantics effectively.

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 verb ('List') and resource ('all registered projects'), specifying the scope with 'with status'. It distinguishes from siblings like 'register_project' (create) and 'write_to_project' (modify), though not explicitly from 'read_from_project' (which might imply reading content vs. listing metadata).

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention if it's for overviews, filtering, or how it differs from 'read_from_project' (e.g., listing metadata vs. reading project data). The description implies a general listing function but lacks context on prerequisites or exclusions.

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

Install Server

Other Tools

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/itsocialist/claude-code-connector-mcp'

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