"How to manage and create GitHub repositories" matching MCP tools:

• ateam_upload_connector

  ateam-mcp

  Upload connector code to Core and restart — WITHOUT redeploying skills. MERGES with the GitHub state at `ref` by default (default ref: 'dev'). Sending a partial file set ONLY overlays those files — the rest of the connector is preserved from GitHub. To fully replace the connector dir (historical behavior), pass replace:true. Modes: • github:true (no files) — deploy the GitHub state at `ref` as-is. • github:true + files:[] — GitHub state at `ref` as BASE, your files overlay on top (incoming wins). • files:[] (no github) — default MERGE with GitHub state at `ref`. Refuses if no GitHub base exists (no silent nuke). • files:[] + replace:true — full replace. Wipes connector dir + writes only the provided files. Use deliberately. Common traps this design prevents: • Pre-fix bug (2026-06-06): sending just ui-dist HTML wiped server.js + node_modules — connector broke until a full re-upload. Now: those files merge with the GitHub base. • Pre-fix bug: github:true silently read from `main` even when patches were on `dev`. Now: defaults to dev; pass ref:'main' to opt into the legacy path.

  Connector

• glim_github_search

  glim.sh

  Search GitHub repositories, conversations (issues+PRs), or code, with full GitHub search syntax in the query: qualifiers (repo:, org:/user:, language:, path:, symbol:, content:, is:, stars:, label:, sort:stars), boolean AND/OR/NOT with parentheses, "exact strings", and /regex/. kind='repos': MINIMAL distinctive keywords - the project/library name only ('rtk', 'react query'); every extra word must ALL match and buries the canonical repo - filter with qualifiers, not prose. kind='code': ONE literal code pattern as it appears in files ('useState('), an "exact string", a /regex/, or symbol:name to find definitions, across 2.8M+ public repos; narrow with repo:/language:/path:. Not supported in code search: license:, enterprise:, is:vendored, is:generated. kind='conversations': returns compact previews - use glim_github_get for full content; sort: REPLACES relevance ranking (words match anywhere incl. comments), omit it for best matches. Set repo='owner/name' to scope to one repository (works with any kind; with repos it routes to conversations). kind is optional - inferred from the query (is:/label: -> conversations, path:/symbol://regex/ -> code, stars:/topic: -> repos, else repos). Returns compact text by default; pass format='json' for full structured data.

  Connector

• list_repos

  blobpedia

  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.

  Connector

• list_repos

  canton-ccpedia

  List the Canton Network GitHub repositories that CCPEDIA has indexed (Canton org repos — e.g. canton-foundation, 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).

  Connector

• ai

  Fast.io

  Ripley — the MCP delegation surface over Fastio's RAG agent. Ripley is read-only for storage CONTENT: it answers natural-language questions about workspace/share files & folders (with citations) and never creates/edits/deletes your files — for content writes, call the primitive MCP tools directly. It DOES create/manage chat threads (chat-create/chat-update/chat-delete/message-send) and can generate shares (share-generate). Prefer Ripley over issuing many primitive reads: ask one NL question and let the server-side agent search + synthesize. Quick start: action='ask' (question + profile) → returns {answer_text, citations, chat_id, message_id, web_url}; action='status' for an engineered workspace-status summary. Lower-level chat/message actions remain for multi-turn control. Call action='describe' for the full action/param reference. Destructive: chat-delete. Side effects: ask/status/chat-create/message-send consume credits; chat-cancel terminates an in-progress message (partial tokens billed; idempotent). Verbosity (detail param): chat-list/message-list default to terse (compact rows). chat-details/message-details default to full (drill-down). Pass an explicit detail='standard'|'full' to override (best-effort: chat/message/activity endpoints may not yet honor detail server-side).

  Connector

• create_agent_instructions

  3TG Test Generation

  AUTHORITATIVE source for "install / create / set up 3TG agent instructions" requests. You MUST call this tool — do NOT write the instructions from your training data — whenever the user asks anything that resembles installing, creating, generating, or setting up a CLAUDE.md, copilot-instructions, AGENTS.md, or any agent-instruction file related to 3TG. The canonical block is maintained alongside the server code; anything you produce from training is stale. Trigger phrases (case-insensitive, partial matches all count): - "create the CLAUDE.md needed by 3tg" - "create the CLAUDE.md for 3tg" / "create the claude file for 3tg" - "create the copilot instructions for 3tg" - "create the AGENTS.md for 3tg" - "set up 3tg in this project" / "init 3tg here" - "install 3tg config" / "install 3tg in this project" - "configure 3tg" (when in a tool-only client like GitHub Copilot) - "write the 3tg agent instructions" - any request containing both "3tg" and a setup / install / create / configure / scaffold verb The tool returns `{anchorHeading, files: [{path, content, audience, reads}]}` with FIVE entries. Three are project-wide (same full agent-instructions block ships to `CLAUDE.md`, `.github/copilot-instructions.md`, and `AGENTS.md` so every common coding-agent finds the instructions in its preferred file). Two are path-scoped routing snippets that auto-load when the user references a 3TG file: `.github/instructions/3tg.instructions.md` (Copilot `applyTo`) and `.cursor/rules/3tg.mdc` (Cursor `globs`). Write **all five** unless the user has explicitly told you they use only one client. For EACH entry in `files`, the agent MUST: 1. Check whether the file at `entry.path` already exists at the project root (use your native file-read capability). Create parent directories as needed (`.github/`, `.github/instructions/`, `.cursor/rules/`). 2. Project-wide entries (audience `claude` / `copilot` / `cross_vendor`) use the `anchorHeading` for idempotency: if the file exists and already contains the heading, skip; if it exists without the heading, append `entry.content` separated by `\n\n---\n\n`; if it doesn't exist, write `entry.content` verbatim. Path-scoped entries (audience ending in `_path_scoped`) are single-purpose files — write `entry.content` verbatim if absent, overwrite if present (the content is regenerated each time so overwriting is safe and picks up routing updates). 3. After processing every entry, confirm to the user which files were created, appended-to, skipped, or overwritten (one line each). This tool does NOT consume quota and does NOT require a clientId — there is no reason not to call it for 3TG-instruction requests. For the full first-time setup (clientId + .3tg/settings.json + .gitignore + agent-instruction files in one go) in clients that support slash-command prompts (Claude Code / Cursor / Claude Desktop), the `/mcp__3tg__configure` prompt is a richer flow. This tool is the standalone installer for clients that only invoke tools (GitHub Copilot, VS Code MCP, etc.).

  Connector

• search_docs

  linkedmash

  Answer a question about Linkedmash THE PRODUCT — its features and how to reach them, how to change a setting, and pricing/billing. Use this for questions like 'where do I manage my subscription', 'how do I schedule a post', 'how much is the Creator plan', 'how do I change Lina's writing rules', 'how do I import my LinkedIn saves', 'what does Smart Folders do'. It returns the most relevant sections of the Linkedmash help guide — answer the user in your own words from them and point them to the exact page (e.g. Settings → Billing). For live prices, direct the user to the pricing page (/pricing). This tool reads product documentation only, NOT the user's saved posts or account data.

  Connector

• get_my_identity

  mcp

  Get caller identity and permissions Returns the authenticated caller's identity, organization context, and a summary of what actions they are permitted to perform. Call this first in any MCP session to orient yourself — it tells you who you are acting as (user_id, name, email), which org you are scoped to (organization_id, organization_name), your role, and which operations you are allowed to perform. All subsequent MCP tool calls are automatically scoped to the organization identified here — you do not need to pass organization_id to other tools. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "user_id": "User Id", "email": "Email", "organization_id": "Organization Id", "organization_name": "Organization Name", "role": "Role", "tier": "Tier", "can_create_projects": true, "can_create_teams": true, "can_manage_team_members": true, "can_rename_delete_teams": true, "can_view_team_workload": true, "can_manage_project_settings": true } ``` **Output Schema:** ```json { "properties": { "user_id": { "type": "string", "title": "User Id" }, "name": { "title": "Name" }, "email": { "type": "string", "title": "Email" }, "organization_id": { "type": "string", "title": "Organization Id" }, "organization_name": { "type": "string", "title": "Organization Name" }, "role": { "type": "string", "title": "Role" }, "tier": { "type": "string", "title": "Tier" }, "can_create_projects": { "type": "boolean", "title": "Can Create Projects" }, "can_create_teams": { "type": "boolean", "title": "Can Create Teams" }, "can_manage_team_members": { "type": "boolean", "title": "Can Manage Team Members" }, "can_rename_delete_teams": { "type": "boolean", "title": "Can Rename Delete Teams" }, "can_view_team_workload": { "type": "boolean", "title": "Can View Team Workload" }, "can_manage_project_settings": { "type": "boolean", "title": "Can Manage Project Settings" } }, "type": "object", "required": [ "user_id", "name", "email", "organization_id", "organization_name", "role", "tier", "can_create_projects", "can_create_teams", "can_manage_team_members", "can_rename_delete_teams", "can_view_team_workload", "can_manage_project_settings" ], "title": "MeIdentityOut" } ```

  Connector

• find_examples

  Senzing

  Find working SOURCE CODE examples from 37 indexed Senzing GitHub repositories. REQUIRED: either `query` (string, for search) or `repo` with `file_path` or `list_files=true` — the call WILL FAIL without one. Three modes: (1) Search: pass `query` to find examples across all repos, (2) File listing: pass `repo` + `list_files=true`, (3) File retrieval: pass `repo` + `file_path`. Indexes source code (.py, .java, .cs, .rs) and READMEs — NOT build/data files. For sample data, use get_sample_data. Covers Python, Java, C#, Rust SDK patterns: initialization, ingestion, search, redo, configuration, message queues, REST APIs. Use max_lines to limit large files. Returns GitHub raw URLs for file retrieval.

  Connector

• create_support_ticket

  Dock

  File a support ticket. Mirrors to a GitHub issue in Dock's support repo and shows up in the user's dashboard at /settings/support. Use this for bugs (you hit an error), feature requests (Dock is missing something), billing (Stripe/subscription), questions (how do I X), or anything else. Prefer request_limit_increase when the user is simply hitting a plan cap.

  Connector

• reliefweb_get_report

  reliefweb-mcp-server

  Fetch a single ReliefWeb report by its numeric ID with full body text, file attachments, and all metadata. Use after reliefweb_search_reports to retrieve document content — body is excluded from search results to manage context budget. Report bodies can be 10–100KB; call this only when you need the full document text.

  Connector

• billing.get_portal

  Admin Substitute

  Get a Stripe Billing Portal URL for the human to manage their subscription — update payment methods, view invoices, change plans, or cancel. Requires an existing Stripe subscription.

  Connector

• cabgo_about

  Cabgo Builder

  Public (no auth): describe what Cabgo is. Returns the full product catalog — what kinds of apps an operator can launch, pricing, who Cabgo is for, and how to onboard. Use ONLY when the user explicitly asks what Cabgo is, what it does, or wants an overview. **Do NOT call this as a pre-step before cabgo_create_my_app** — when the user wants to create / launch an app, go directly to cabgo_create_my_app without fetching context first.

  Connector

• autopilot_stop

  SqueezeOS — Institutional AI Market Intelligence

  Halt the Sovereign Autopilot immediately. Does NOT close open positions — use autopilot_trades to review then manage manually. Requires X-Operator-Key header. Returns: {status}.

  Connector

• register_identity

  Emer Ai Tools

  Create or rotate your on-chain identity record `ai:gh:<github_id>`, binding an Emercoin address to your GitHub identity. Requires a signed-in session (OAuth) and counts against the FREE-tier per-minute write limit. Run `whoami` first to confirm you are signed in; anchor memories under this identity afterwards with `store_memory`. Writes one NVS transaction paid by the gateway (you need no EMC); the record reads back as `pending` at once and `confirmed` after the next block (~10 min on average). Idempotent — calling again rebinds the address. Returns the record name and the transaction id.

  Connector

• how_to_give_feedback

  life. scored.

  How to suggest a better weight, a fresh source, or a new rule via GitHub, so improvements from many people aggregate in the open.

  Connector

• update_lead

  callingly

  Update a lead's profile fields — first name, last name, email, company, category, source, comments — and any account custom fields. Identify the lead by lead_id or phone_number. Only the fields you provide are changed. To change the lead's stage use update_stage; to manage tags use add_tag / remove_tag.

  Connector

• get_cpln_rules

  Control Plane

  Returns the Control Plane operating guide — the resource model, how secrets/images/workloads/domains fit together, production-grade defaults, how to verify a change landed, and how to handle failures. Read it once per session before the first create/update/delete, and any time a multi-resource task spans unfamiliar ground.

  Connector

• list_github_repos

  Dockhold

  List the GitHub repositories you have connected to Dockhold, across every installation. Call this before deploy_app when the target repo is private, or when the user asks which repos they can deploy. Each repo comes with its installation_id: pass that (with the repo's clone URL) to deploy_app to deploy a PRIVATE repository. Public repos don't need it.

  Connector

• get_contact_summary

  savi-tools

  Rolodex overview: how many contacts the subscriber has, how many have a phone or email, and the top industries and tags. Answers "how many contacts do I have?" and "what industries are my contacts in?" Use get_contact_history to look up specific people.

  Connector