Skip to main content
Glama
Presh-AR

codescan-mcp-server

by Presh-AR

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CODESCAN_URLYesURL of your Codescan instancehttps://app.codescan.io
NODE_OPTIONSNoNode.js runtime options--experimental-specifier-resolution=node
CODESCAN_TOKENYesAuthentication token for Codescan API
CODESCAN_PROJECTNoDefault project key
CODESCAN_COMPONENTNoDefault component key
CODESCAN_ORGANIZATIONNoOrganization key for Codescan Cloud

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
projectsC

List all Codescan projects

metricsC

Get available metrics from Codescan

issuesC

Get issues for a Codescan project

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: listing projects, retrieving issues for a project, and fetching metrics. There is no overlap or ambiguity.

Naming Consistency4/5

All tool names are single nouns, which is consistent. Adding verbs (e.g., list_projects) would make them more descriptive, but the pattern is uniform.

Tool Count4/5

3 tools is a reasonable number for a focused code scanning server. It covers the core actions without being overly sparse.

Completeness3/5

The server covers listing projects, retrieving issues, and getting metrics. Missing are details on individual projects, issue filtering, or update/delete operations, but for a read-only scanner it is fairly complete.