Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DPR_ACTOR_IDNoOptional: configure the driving agent. Defaults to claude-code.claude-code
DPR_DATABASE_URLNoOptional: database URL for collaboration state.
DPR_PRINCIPAL_IDNoOptional: configure who this server instance acts as. Defaults to human:$USER.human:$USER
DPR_WORKSPACE_ROOTNoOptional: where workspaces live.
DPR_REPOSITORY_ROOTNoOptional: where projects live.

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
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_projectC

Create a new Git-backed project.

list_projectsA

List all projects known to this server.

list_filesA

List files within a project (optionally under a subpath) at HEAD.

search_filesC

Search file contents within a project's default branch checkout.

get_project_statusC

Get a summary status (branches, open changes, active workspaces) for a project.

read_fileB

Read a file's content from within an active workspace.

create_fileC

Create a new file within an active workspace.

edit_fileC

Edit (overwrite) an existing file within an active workspace.

delete_fileC

Delete a file within an active workspace.

get_historyC

Get commit history for a project, optionally scoped to a path.

get_revisionC

Get details for a single commit revision.

get_diffB

Get a structured diff between two revisions in a project.

create_workspaceB

Create an isolated Git worktree workspace for making changes to a project.

get_workspaceC

Get details of a workspace by id.

list_workspacesA

List active workspaces for a project.

delete_workspaceB

Delete (remove) a workspace you own.

create_changeC

Create a Change Request from the commits in a workspace.

get_changeB

Get a Change Request by id.

list_changesA

List Change Requests for a project, optionally filtered by status.

update_changeC

Update a Change Request's rationale and refresh its head revision.

abandon_changeD

Abandon a Change Request.

review_changeC

Record a review (APPROVED, CHANGES_REQUESTED, or COMMENTED) on a Change Request.

approve_changeC

Convenience wrapper: approve a Change Request.

request_changesC

Convenience wrapper: request changes on a Change Request.

check_mergeabilityB

Check whether a Change Request can merge cleanly into the project's default branch.

merge_changeB

Merge an approved, conflict-free Change Request into the project's default branch.

rebase_changeB

Rebase a Change Request's workspace branch onto the current default branch.

get_conflictsC

Get structured conflict information for a conflicted Change Request.

propose_conflict_resolutionA

Propose a resolution to a conflicted Change Request, using commits already made in a separate resolver workspace. This creates a new, independently reviewable Change Request linked to the original conflict.

apply_conflict_resolutionC

Apply (merge) a previously proposed and reviewed conflict resolution. Subject to the same approval policy as any other merge.

rollback_changeA

Roll back a previously merged commit on the project's default branch by creating a new forward commit that restores the prior state (never rewrites history).

get_provenanceC

Get the complete provenance record for a Change Request.

Prompts

Interactive templates invoked by user choice

NameDescription
review_changeAsk the model to review a Change Request thoroughly.
summarize_changeAsk the model to summarize a Change Request for a human reviewer.
explain_conflictAsk the model to explain a merge conflict in plain language.
summarize_historyAsk the model to summarize a project's recent history.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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/Charan-Sharan/dpr-mcp'

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