SourceCraft MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOURCECRAFT_BASE_URL | No | Base URL for the SourceCraft API. Optional, defaults to https://api.sourcecraft.tech. | |
| SOURCECRAFT_API_TOKEN | Yes | Your SourceCraft API token. Obtain from Settings → Access → Personal Access Tokens. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| _list_repositoriesC | List repositories for a user or the authenticated user. Args: username: Username to list repos for (None for authenticated user) page: Page number per_page: Items per page |
| list_organization_repositoriesB | List repositories in an organization. Args: org: Organization name page: Page number per_page: Items per page |
| _get_repositoryC | Get detailed information about a repository. Args: owner: Repository owner repo: Repository name |
| create_repositoryA | Create a new repository for the authenticated user. Args: name: Repository name description: Repository description visibility: Repository visibility (public, internal, private) |
| update_repositoryC | Update repository settings. Args: owner: Repository owner repo: Repository name description: New description (optional) default_branch: New default branch (optional) visibility: New visibility (optional) |
| delete_repositoryB | Delete a repository. Args: owner: Repository owner repo: Repository name |
| list_branchesC | List branches in a repository. Args: owner: Repository owner repo: Repository name page: Page number per_page: Items per page |
| list_tagsB | List tags in a repository. Args: owner: Repository owner repo: Repository name page: Page number per_page: Items per page |
| get_file_treeA | Get the file tree of a repository. Args: owner: Repository owner repo: Repository name revision: Git reference (branch, tag, or commit SHA). Uses default branch if empty. path: Path within repository. Root if empty. recursive: Whether to retrieve recursively |
| _list_issuesD | – |
| _get_issueD | – |
| _create_issueD | – |
| _update_issueD | – |
| _close_issueD | – |
| _reopen_issueD | – |
| _list_issue_commentsD | – |
| _add_issue_commentD | – |
| _list_pull_requestsD | – |
| _get_pull_requestD | – |
| _create_pull_requestD | – |
| _update_pull_requestD | – |
| _merge_pull_requestD | – |
| _publish_pull_requestD | – |
| _discard_pull_requestD | – |
| _list_pr_reviewersD | – |
| _add_pr_reviewerD | – |
| _set_review_decisionD | – |
| _list_ci_runsD | – |
| _get_ci_runD | – |
| _get_workflowD | – |
| _get_cube_logsD | – |
| _get_artifactsD | – |
| _trigger_workflowsD | – |
| _list_releasesD | – |
| _get_releaseD | – |
| _get_latest_releaseD | – |
| _create_releaseD | – |
| _update_releaseD | – |
| _publish_releaseD | – |
| _discard_releaseD | – |
| _get_current_userD | – |
| _get_userD | – |
| _list_my_issuesD | – |
| _list_user_pull_requestsD | – |
| _list_organizationsD | – |
| _get_organizationD | – |
| _list_organization_repositoriesD | – |
| _list_organization_membersD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 48 tools
There are duplicate tools (`_list_organization_repositories` and `list_organization_repositories`) and several similar lifecycle actions (`_create_release` vs `_publish_release`, `_update_pull_request` vs `_publish_pull_request`) that are hard to tell apart. Vague names like `_trigger_workflows` and `_get_cube_logs` further obscure their exact purpose relative to other CI tools.
Most tools follow a snake_case verb_noun pattern, but the leading underscore prefix is applied inconsistently: some tools like `create_repository`, `list_branches`, and `get_file_tree` have no underscore. The duplicate `_list_organization_repositories` / `list_organization_repositories` pair and odd names like `_get_cube_logs` also break the naming pattern.
48 tools is a very large surface for a source-management server, especially when several tools appear duplicative or could be consolidated (`_publish_release` vs `_discard_release`, `_trigger_workflows` vs `_get_workflow`). The scope spans users, orgs, repos, issues, PRs, releases, and CI, which feels heavy rather than focused.
Major workflows for repositories, issues, pull requests, releases, and CI are covered with CRUD/lifecycle actions in most areas. However, there are notable gaps for a source-management tool: no commit listing/inspection, no branch or tag creation/deletion, and no repository search or org member management beyond listing.