Integrations

Other MCP Clients

Using Stellarion with other MCP-compatible tools

Stellarion works with any tool that supports the Model Context Protocol (MCP).

MCP Overview

The Model Context Protocol is an open standard for connecting AI assistants to external tools and data sources. Stellarion implements an MCP server that exposes its 12 analysis tools.

General Setup

1. Install Stellarion

npm install -g stellarion

2. Configure Your MCP Client

Add Stellarion as an MCP server in your client's configuration:

{
  "command": "stellarion",
  "args": []
}

The exact configuration format depends on your MCP client.

3. Connect

Start your MCP client. It should automatically connect to Stellarion and make its tools available.

Available Tools

When connected, these tools are available:

ToolDescription
search_semanticNatural language code search
search_patternRegex pattern matching
get_code_elementExtract functions/classes
analyze_structureDependency analysis
analyze_qualityCode quality metrics
analyze_impactChange impact assessment
index_projectIndex for semantic search
project_infoProject metadata
generate_reportQuality reports
find_refactoringRefactoring opportunities
extract_endpointsAPI endpoint extraction
batch_analyzeBulk file analysis

Server Options

Working Directory

By default, Stellarion uses the current working directory. You can specify a project path:

{
  "command": "stellarion",
  "args": ["/path/to/project"]
}

Environment Variables

Set environment variables for the server:

{
  "command": "stellarion",
  "args": [],
  "env": {
    "OPENAI_API_KEY": "sk-..."
  }
}

Testing the Connection

Once connected, you should be able to:

  1. List available tools (12 tools)
  2. Call tools with parameters
  3. Receive structured responses

Troubleshooting

Server Not Starting

npm list -g stellarion

stellarion status

Tool Errors

Check that:

  • The project path exists
  • Required files are accessible
  • Environment variables are set correctly

Connection Timeout

  • Increase your client's connection timeout
  • Check for port conflicts
  • Verify the command path is correct