"How to access and read GitLab repositories" matching MCP tools:

• get_principlesA

  turva-mcpA

  Returns turva.dev's engagement principles: async-only, least access, the result shows up in scanner numbers, and open and verifiable. Use this when a user asks how turva.dev works with clients or what rules an engagement follows. For what is sold and what it costs use get_services instead, and for how to start use get_contact. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy.

  ConnectorNo auth

• list_campaignsA

  argo-mcpA

  List all Argo campaigns the current grant token has access to, including the access level ("read" or "read+write") for each. Call this first when the user has not provided a campaign ID. Each entry includes both `campaignName` and `id` (shown inline as `[id: …]` and also in structuredContent.idMap). Use the `id` verbatim for any subsequent tool call that takes a `campaignId`. In prose to the user, refer to campaigns by `campaignName`; do not print the raw `id` unless asked.

  ConnectorNo auth

• list_kitsA

  Moltline Catalog — 138 Agent Skills & PersonasA

  List the 12 themed kits with pricing and member products. FREE. Takes no arguments. Returns a list of kit objects, each {"slug": ..., "name": ..., "price_usd": N, "tagline": ..., "members": ["product-slug", ...], "availability": ...}. Use a kit's slug with get_full_kit (premium). Kits are not sold standalone on any marketplace: price_usd is the bundle's reference value, and All-Access is how a caller actually unlocks one. Use when the caller asks about bundles or bundle pricing. Not for individual products (search_catalog) and not for a kit's full contents (get_full_kit). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

  ConnectorNo auth

• get_corpus_coverageA

  SRI — MCP Server InspectorA

  No arguments. Returns how many MCP servers have been read at source level, and the share of them with each category of finding (credential access, network egress, install-time execution, prompt-injection surface). Use this to judge whether checking a specific server is worth it before you look one up. It reports aggregate counts only - no per-server findings, and no verdict about any individual server.

  ConnectorNo auth

• account_ai_accessA

  ClusterHackA

  How the signed-in user sees and revokes AI access to their own account — read this instead of looking for a tool that lists or cuts off connected clients, because there is deliberately no such tool. The controls over AI access (list connected clients, revoke one, list and end live MCP sessions, read the record of what a client did as them) are gated to the account holder signing in directly: a browser session, a JWT, or an API token they hold themselves. A connected AI client — including this one — is refused, on purpose. If it were not, a client could revoke its rivals, enumerate the user's other connections, or read the trail it leaves behind. So this tool tells the user where to go and what they will find; it makes no API call and cannot fail. Also names where account deletion and data export live: the export has a tool (`account_export_data`), the deletion deliberately does not.

  ConnectorNo auth

• get_contactA

  turva-mcpA

  Returns who runs turva.dev and the official ways to reach it: the operator and business details, the email address, the Signal link, the LinkedIn profile, the correspondence languages, the first-reply time and the access an audit needs. Use this when a user asks who is behind turva.dev, how to contact it, how to start an audit or what access has to be granted. For what is sold and what it costs use get_services instead. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy.

  ConnectorNo auth

• list_kitsA

  Moltline StudioA

  List the 12 themed kits with pricing and member products. FREE. Takes no arguments. Returns a list of kit objects, each {"slug": ..., "name": ..., "price_usd": N, "tagline": ..., "members": ["product-slug", ...], "availability": ...}. Use a kit's slug with get_full_kit (premium). Kits are not sold standalone on any marketplace: price_usd is the bundle's reference value, and All-Access is how a caller actually unlocks one. Use when the caller asks about bundles or bundle pricing. Not for individual products (search_catalog) and not for a kit's full contents (get_full_kit). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

  ConnectorNo auth

• list-provider-repositoriesA

  docuwriterA

  Use this when the user wants to choose a repository from a connected GitHub, GitLab, Bitbucket, or Azure DevOps provider before creating an Autopilot link. Read-only external-provider lookup: fetches repository choices or returns reauthorization/browser guidance. Requires provider and space_id.

  ConnectorOAuth

• set_access_role_mailbox_accessA

  Higgs HubB

  How far an access role's agents may reach into one mailbox: the access level (write = everything its capabilities allow, read = search and read only, none = hidden), which folders its file tools may use (all / only these / all except these, by folder path), and which calendars (all / only these / all except these, by calendar name). Give only the parts you want to change; the others stay as they are. list_access_roles shows the current standing. This only stages a request: the owner opens the link in their browser, reviews it, and approves it there with their agent PIN. Never ask for or accept the PIN in chat.

  ConnectorOAuth

• precis_orientationA

  Précis Finance MCPB

  Call this first. Returns how to use Précis over this connector: the data model (scenarios, metrics, statements, dimensions), the reporting-tool variants, and how to build charts. Read it before composing queries.

  ConnectorNo auth

• list_github_discussionsA

  canton-ccpediaA

  List GitHub Discussions from Canton Network and Digital Asset repositories cached by CCPEDIA, sorted by recency (newest first). Filter by repo or category, or call with no filter to see which repos are present. CANTON-ONLY and read from CCPEDIA's cache, NOT the live GitHub API or the user's own repos (use a GitHub MCP for those). This is GitHub Discussions: distinct from the Canton web forum (get_discussion) and the sync.global mailing lists (list_mailing_threads). Use get_github_discussion for full body + comments.

  ConnectorNo auth

• brainkb_list_spacesA

  brainkbB

  List spaces the user can see (their own/member spaces + public ones), each annotated with THIS caller's permission so you know what they may do: - your_role: 'owner' | 'editor' | 'viewer' | null (their space membership) - is_owner: they own the space - access: 'owner' | 'member' | 'public' (how it's available to them) - can_write: their space role permits ingest (owner/editor) — a real ingest also needs the 'ingest' capability + any per-space access rules. Use this to tell the user which spaces they can read vs. write vs. only see as public.

  ConnectorNo auth

• write_to_repoA

  SHPBL: Repository Audit & RepairA

  Land finished work in a repository as a pull request: pass the files you wrote (full new contents, not diffs) and this opens a branch and a PR for the human to review and merge. Nothing is ever pushed to the default branch. Requires a SHPBL Practitioner key and the SHPBL GitHub App installed on that repository (or a one-off `github_token`). The caller chooses the repository — ask which one, or call `list_repos` first; never assume. Where things go: Harvest output belongs under `.shpbl/` in **the caller's own repository** — the person who asked for the run — and never in the repository that was harvested. Those are frequently not the same repository: a run may read a public open-source project, or a repository the caller merely has access to, and writing a harvest back into a source repository would be putting our output into somebody else's software. Sources a run may read: public repositories that carry a proper open-source license, the caller's own repositories, or private repositories the caller has access to. The server never reads a repository the caller has no right to read, and it never absorbs customer harvests back into the public library. - `.shpbl/README.md` — the index of their capability library (this tool scaffolds it when it is absent). - `.shpbl/<run-seal>/LEDGER.md` — the folded ledger for one run. - `.shpbl/<run-seal>/REPORT.html` — the branded report, if one was produced. - `.shpbl/<capability-name>/` — a capability kept as source, one folder each. - `.shpbl/COMPOSITES.md` — your own composites: capabilities this run invented for your repository by fusing parts that did nothing alone. Record each as `- <name> — <what it fuses> — <why neither part sufficed>`. These are yours and stay private; SHPBL's global composites ledger is fed only by Governor-keyed published runs, so never send yours anywhere and never expect them to appear there. If the harvested repository is not the caller's own, the harvest still lands in the caller's `.shpbl/` and the source is named in provenance. Ask the person which of their repositories is the home for their library if it is not obvious, and stop for that answer rather than guessing. Give each kept capability a one-line contract in `.shpbl/README.md`, in the form `- <name> — <path> — <contract>`. That index is what makes the library reusable: on the next run, read it and pass those entries as `own_library` to `evaluate_repo`, `fix_repo` or `run_gauntlet`, and the run will tell you which concerns you already solved before citing anything new. Those entries stay yours — they are held for the call and never stored by SHPBL. Repairs are the exception: write the repaired file at its own path, never under `.shpbl/`.

  ConnectorNo auth

• continental_how_to_joinA

  The ContinentalA

  How an AI agent gets access to The Continental: the free Porch pass (no human needed: hashcash + Ed25519), and membership through an operator (price, limits, the three steps they take, the text to forward to them). Also how to configure this server once you have a key. Call this first if you have no key.

  ConnectorNo auth

• get-created-pull-requests-toolA

  CoderbudsA

  Count pull requests OPENED over a recent window (default 1 day), broken down per repository and per author, with a human-vs-bot/dependabot split. Use this whenever the question is how many pull requests were created, opened or raised — today, this week, on a repo, or across the team — and especially when someone asks to see it "per repo" or "by repository". Prefer this over a per-person activity breakdown for any total. It counts from the team's repositories rather than its member list, so it includes authors who have no Coderbuds account (reported as `authors_without_member` and `created_by_non_members`) and excludes a member's work in repositories this team does not ship. A member-first count gets both of those wrong. The result carries its own denominator: `repositories` is exactly the list the numbers came from, so you can answer "which repos is this based on" from the same call. Slugs that match no team repository come back in `unmatched_repositories` instead of quietly counting zero. Opened is counted by the time the provider recorded the pull request being opened. That is a different set from merged in the window — use `get-merged-pull-requests` for merges, and never present the two as reconciling.

  ConnectorOAuth

• imagine_list_my_worldsA

  Embers: Tabletop RPG ToolkitA

  List the worlds the calling user owns or has access to via membership. Returns slim catalog-card fields per world (id, name, summary, image, link, createdAt, updatedAt). To read a specific world's full body and configuration, call imagine_get_world with the id.

  ConnectorOAuth

• get_startedA

  VeriflyA

  Call this FIRST if you have no Verifly API key. Returns how Verifly works and how to get access with no human: pay-as-you-go email verification API, 100 free credits on self-registration, no monthly fee. No API key required to call this tool.

  ConnectorNo auth

• get_helpA

  sinoconnection-esim-mcpA

  Answer customer support and policy questions about SinoConnection eSIMs: the REFUND POLICY, how to INSTALL (with step-by-step videos), activation, HOW THE NO-VPN CHINA ACCESS WORKS (roaming / exit IP — see faq.how_no_vpn_works), and how to get support. Call this whenever the customer asks about refunds, cancellations, installation/setup, activation, how it works, what IP / does it bypass the firewall, or help — do NOT answer these from memory (especially the IP/firewall question); relay this authoritative content verbatim in meaning.

  ConnectorNo auth

• list_reposA

  canton-ccpediaA

  List the Canton Network GitHub repositories that CCPEDIA has indexed (Canton org repos such as canton-foundation and Daml/Splice, excluding the dev-fund proposals repo), with the count of issues+PRs indexed per repo. CANTON-ONLY and read from CCPEDIA's cache. This is NOT a live GitHub API and does NOT list the user's own repos (use a GitHub MCP for that).

  ConnectorNo auth

• list_reposA

  blobpediaA

  List the GitHub repositories that blobpedia has INDEXED for Celestia, with item counts. Read-only view of the Celestia index on this server — does NOT browse your GitHub account or arbitrary repos (use a dedicated GitHub tool for that). Zero arguments.

  ConnectorNo auth

• rigs.listA

  GlasswarpA

  List Windows machines (rigs) paired to this API key: id, name, online, api_access_enabled, and USABLE flag. Read-only — does not start a session. Call first before start_session. A rig is USABLE only when online AND the owner enabled API access. If none are USABLE, tell the user to install the host agent, pair in Console → Rigs, and enable API access — never ask for OS passwords.

  ConnectorNo auth