Skip to main content
Glama
793,815 tools. Updated 2026-11-17 07:13

"Using Git with Python for Operations" matching MCP tools:

  • Fast code search across any public git repo. Returns file paths, line numbers, and code snippets with context. Supports regex, boolean queries, fuzzy matching, and structural filters (declarations, usages, strings, comments). Dependency/build directories excluded by default. Searching for leaked secrets? Call code_analyze instead and read security_summary — it runs a real secret and credential scanner over the whole repository, where searching for key prefixes like "sk-", "ghp_" or "AIza" only matches the spellings you happened to think of.
    ConnectorNo auth
  • Submit an uploaded PDF for faxing. Step 1 (before this tool): upload the PDF over plain HTTP multipart, using any HTTP client you have — shell, JavaScript fetch with FormData, Python, etc.: curl -F "file=@document.pdf" https://www.sendthisfax.com/api/upload fetch("https://www.sendthisfax.com/api/upload", {method: "POST", body: formDataWithFile}) The response contains fax_public_id and page_count. PDFs must be unencrypted, at most 50 MB and 1000 pages. Step 2: call this tool with the fax_public_id and the recipient fax number. Two modes: - With an API key (Authorization: Bearer stf_live_... on this MCP connection): the fax price is debited from the prepaid credit balance and sending starts immediately — no checkout, no browser. sender_email and billing_country are optional (they default to the key's records). Buy credits at https://www.sendthisfax.com/en/credits. - Without an API key: sender_email and billing_country are REQUIRED and the tool returns a checkout_url the USER must pay in a browser; the fax is sent automatically once paid. In both modes, poll get_fax_status until status reaches "delivered" or "failed" (failures after payment are auto-refunded). For integration testing, +19898989898 is the designated test recipient number.
    ConnectorNo auth
  • Check Python source without running it: parse, lint (ruff), type-check (mypy), AST security policy, credential scan. Safe on code you do not trust. Use it on every Python file you generated or edited, before writing it to disk. Alternatives: repair_python to get the corrected source instead of the diagnosis; execute_python to prove the code runs. Auth: a key is required. A free key covers this call, 25 per day, then HTTP 429; get one with POST /v1/keys. Credits are bought without an account, 1 per call: GET /v1/pricing says where to send the xDAI. Or pay for this one call with no key at all: call it without one and the result carries x402 payment requirements ($0.01 in USD Coin on eip155:8453); sign them and repeat the call with the payment in _meta['x402/payment']. Arguments: code: the whole file, 1..200000 bytes of UTF-8 measured after encoding (empty is refused with 400, larger with 413); a fragment is fine, but line and column numbers in the answer count from 1 in what you sent. language: must be 'python'; anything else is 400, and the field may be omitted. Of options only transpile_to (e.g. 'javascript', which returns a translated copy in transpiled) acts here; timeout_s, max_iterations, optimize, examples and expected_output need a pass that rewrites or runs the code, so send code alone. Ignored options are not refused, so a call that sets them looks like it worked; and code that does not parse is answered rather than refused: valid=false with the syntax error located, which is the point. Returns valid, score 0..1, diagnostics (rule, message, line, column), security findings, fixes, fixed_code and runtime; see outputSchema. The code and its verdict are retained to improve the service.
    ConnectorNo auth
  • Before security-sensitive tooling or agent operations: find recent threads relevant to a task, with source links, provenance and matching keywords. Keyword overlap on title, tags and excerpt over the last 200 active threads; not semantic search and not the full archive (use search for that). Seeds excluded by default.
    ConnectorNo auth
  • Enumerate and inspect the validated operations scene_apply accepts — call this BEFORE reaching for scene_script. The DSL is large (mesh editing, booleans, lathe/loft/sweep, curves, UV unwrap, modifiers, materials, lights, cameras, render settings, geometry nodes, batch and query ops), so most modelling does NOT need raw bpy. No args: every namespace with counts. guide=true (or op="guide" for older connector catalogs): full operating guide. namespace="mesh": that namespace's operations. Repeated details are object.radial_array or object.array_along_curve (no "pattern" namespace). Use world.update for the environment; validation is the separate scene_validate tool. search="boolean": ranked matches. op="mesh.bevel": the full JSON Schema with types, ranges and defaults. Schemas are introspected from the validator itself, so they are always exactly what scene_apply will accept. Full schemas are returned once in structuredContent; format="text" returns them in text instead. This tool is READ ONLY and free — it queues no job, spends no compute and changes nothing — so it is always safe to retry, including after a transport-level error.
    ConnectorAPI key
  • PERMANENTLY delete an already-deleted repository now, instead of waiting for its restore window to end. IRREVERSIBLE: the git data, LFS objects, issues, PRs, releases, packages, CI history and settings are removed and cannot be restored (data already in the instance's backups ages out on the backup schedule). Only works on a repository already deleted with merjax_delete_repo; `confirm` must be its full name (owner/name). Owner (personal owner, or an org owner) or a site admin; needs 'admin' scope. Audited as repo.purge. Returns {purged: true, id, full_name}.
    Connector
    Destructive
    OAuth

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    Odds are, most of what you want to build is already open source. Tell your AI agent what you're making, and it finds it: which repos to use as they are, which to adapt, and what's left for you to write. Every repo it names is real, licensed for your use or flagged, and checked live.
    3
    331 npm
    1
    MIT

Matching MCP Connectors

  • Run Python code from natural language prompts, with optional PyPI package install.

  • Buy private git repos and agent skills with USDC over x402. Read the manifest free, then pay.

  • Draws N unique random cards from the 78-card deck using cryptographic randomness (Python secrets.SystemRandom). Every call is independent — there is no session state. WORKFLOW: BEFORE: None — standalone. AFTER: None — interpret drawn cards using their active_meaning and active_keywords fields. INPUT CONTRACT: count (int 1–78, default 1) — Number of unique cards to draw. Example: 1 (daily pull), 3 (simple reading), 10 (Celtic Cross), 78 (full deck shuffle). Values outside 1–78 are rejected locally with MCP INVALID_PARAMS. allow_reversed (bool, default false) — When true, each drawn card independently has a 50% chance of reversal (cryptographically random, not seeded). DO NOT CONFUSE WITH: asterwise_get_tarot_card_of_the_day — deterministic daily card, same for all callers. asterwise_get_tarot_three_card_spread — positional read with named positions and meanings. asterwise_get_tarot_celtic_cross — 10-card positional spread. Full output and error contract: https://docs.asterwise.com/mcp/tools/draw-tarot-cards/
    ConnectorOAuth
  • FREE. Full catalog of Quantum Artificer: the 5 domains, their operations, input-spec shapes, limits, and prices. Call this first to learn how to build the `spec` for the paid compute tools. No wallet needed.
    ConnectorNo auth
  • CANONICAL ENTRY for LLM brand discoverability assessments. Prefer this over start_discoverability_assessment. Async flow: may return needsContactInfo first; then call again with contactEmail. Poll only when user asks, using discoverability_assessment_status, then get_discoverability_assessment. Not for website SEO or reliability.
    ConnectorNo auth
  • Registers the project if it is new, attaches whatever source you give it, and deploys it using the application's Deployment workflow. Direct applications go to Production; Staged applications go to Development. Returns the live URL, or a deployment id to poll if the build is still running. **You do not decide whether this project needs git.** Send what you have and SpringRoll works it out: • a pushed git remote → pass `repositoryUrl` (and `ref` if not the default branch) • no remote, or uncommitted work → pass `archive`, a base64 tar+gzip of the source: tar --exclude=node_modules --exclude=.next --exclude=.git --exclude='.env*' \ -czf - . | base64 -w0 • both → SpringRoll builds from git, and falls back to your files if the ref cannot be resolved (an unpushed branch, typically) • neither, on an app that already exists → redeploys its current source Upload SOURCE, not build output: SpringRoll runs the build. node_modules, .next, dist, build, out, coverage and .log files are dropped automatically and reported. Every .env file and .git/ is REFUSED outright, naming the offending path: configuration belongs in SpringRoll, not in the bundle. Upload limits are about 3 MB compressed on the wire (a platform request-body cap, not a preference), 20 MB expanded, 2000 files, 512 KB per file; a project past them should pass `repositoryUrl` instead, which SpringRoll clones directly with no size limit. Sending the same files twice is free, because bundles are addressed by content. Direct to Production skips workflow approvals but keeps production safety checks. Staged applications continue to use explicit promotion and approvals.
    ConnectorNo auth
  • Validates a Python automation script that runs OUTSIDE the game, on three axes: Python syntax (using the real interpreter), Minecraft commands embedded in the script (against the official command index), and the shape of the /connect WebSocket message envelope. For behavior pack scripts use validate_script instead — Python does not run inside a pack. The embedded command check is the most valuable one: a command written from memory can look syntactically fine and still do nothing in the game. Only strings starting with / are treated as commands. If syntax could not be checked, syntaxChecked is false in the result; ok:true alone does not mean the syntax is valid.
    ConnectorNo auth
  • Raw file/git access at the indexed commit, for cloud agents with no clone; with a clone prefer your own Read/Grep/git. Ops: - read: content of filePath, whole file or slice startLine..endLine. ifHash (a prior read's hash) returns {unchanged:true}, no content. compact:true strips blank/comment-only lines. - list: files+subdirs at path. grep: ripgrep pattern (glob/pathPrefix). tree: layout from path. stat: size/lines/language/binary for filePath. blame: authorship for filePath. diff: fromSha..toSha. Keys: {op:"read",filePath:"src/a.ts"}, {op:"grep",pattern:"foo"}, {op:"list",path:"src"}. filePath is the file, path the directory. Gated by the Source Access add-on; else source_access_required.
    ConnectorNo auth
  • Draws N unique random cards from the 78-card deck using cryptographic randomness (Python secrets.SystemRandom). Every call is independent — there is no session state. WORKFLOW: BEFORE: None — standalone. AFTER: None — interpret drawn cards using their active_meaning and active_keywords fields. INPUT CONTRACT: count (int 1–78, default 1) — Number of unique cards to draw. Example: 1 (daily pull), 3 (simple reading), 10 (Celtic Cross), 78 (full deck shuffle). Values outside 1–78 are rejected locally with MCP INVALID_PARAMS. allow_reversed (bool, default false) — When true, each drawn card independently has a 50% chance of reversal (cryptographically random, not seeded). DO NOT CONFUSE WITH: asterwise_get_tarot_card_of_the_day — deterministic daily card, same for all callers. asterwise_get_tarot_three_card_spread — positional read with named positions and meanings. asterwise_get_tarot_celtic_cross — 10-card positional spread. Full output and error contract: https://docs.asterwise.com/mcp/tools/draw-tarot-cards/
    ConnectorOAuth
  • Read one of Sendora's documents whole, as Markdown: a guide (sendora://docs/…), an API operation (sendora://reference/…), the error codes (sendora://errors) or an SDK's README and rules for agents (sendora://sdk/readme and sendora://sdk/skill for TypeScript, sendora://sdk/python/readme and sendora://sdk/python/skill for Python, sendora://sdk/php/readme and sendora://sdk/php/skill for PHP, and sendora://sdk/laravel/readme for Laravel). sendora://index lists every document; search_docs finds the right one.
    ConnectorNo auth
  • Authoritative REST API reference for writing integration code into the user's app. Base URL: https://api.volanea.com — auth is `Authorization: Bearer <secret key>`; sends accept an `Idempotency-Key` header. Use this instead of guessing endpoint shapes or SDK names. THREE MODES, and the default is the expensive one: `{ resource, indexOnly: true }` lists every operation's id, method, path, and one-line summary with NO schemas (a few KB); `{ resource, operations: [ids] }` returns full request/response schemas for just those operations, plus only the schemas they reference; `{ resource }` alone returns the entire resource, which for Campaigns or Contacts is 40-50 KB of one reply. Start with indexOnly, then expand the two or three operations you are actually going to call — every byte of a reference dump re-enters your context on every later turn.
    ConnectorNo auth
  • Authoritative REST API reference for writing integration code into the user's app. Base URL: https://api.volanea.com — auth is `Authorization: Bearer <secret key>`; sends accept an `Idempotency-Key` header. Use this instead of guessing endpoint shapes or SDK names. THREE MODES, and the default is the expensive one: `{ resource, indexOnly: true }` lists every operation's id, method, path, and one-line summary with NO schemas (a few KB); `{ resource, operations: [ids] }` returns full request/response schemas for just those operations, plus only the schemas they reference; `{ resource }` alone returns the entire resource, which for Campaigns or Contacts is 40-50 KB of one reply. Start with indexOnly, then expand the two or three operations you are actually going to call — every byte of a reference dump re-enters your context on every later turn.
    ConnectorNo auth
  • Changes an existing neonloops workflow's draft: adds, configures, connects, removes or renames steps and edges, tidies the layout, and sets the name, description, status, project or cost cap. Make a draft with workflows_create and read it with workflows_get first; runs_test_draft tries the result and workflows_publish makes it live. Operations run in order and save in one write against the revision you pass: when one is refused none applies, and a change made since your read is never overwritten. Settings are saved after the checks and before the operations. A removed step is gone; re-adding it makes a new step and id. The answer gives the new revision, the ids of new steps and edges, and whether a run would accept the graph.
    Connector
    Destructive
    API key
  • Returns the append-only change history (most recent first) of a ground: node/edge/api/bug create, update (with a field-level diff {from,to}), delete, and plan_commit. Each event carries the actor ("user:<id>" for humans, "token:<id>" for agents/automation), a summary label, and for updates a diff. Use it to answer "what changed, when, and by whom" — e.g. a bug's status transitions or a node's edits over time. Filter with entityType/entityId to get a single entity's timeline. Note: git commits recorded via record_commit live in a node's metadata.commits, not here.
    ConnectorNo auth
  • Registers the project if it is new, attaches whatever source you give it, and deploys it using the application's Deployment workflow. Direct applications go to Production; Staged applications go to Development. Returns the live URL, or a deployment id to poll if the build is still running. **You do not decide whether this project needs git.** Send what you have and SpringRoll works it out: • a pushed git remote → pass `repositoryUrl` (and `ref` if not the default branch) • no remote, or uncommitted work → pass `archive`, a base64 tar+gzip of the source: tar --exclude=node_modules --exclude=.next --exclude=.git --exclude='.env*' \ -czf - . | base64 -w0 • both → SpringRoll builds from git, and falls back to your files if the ref cannot be resolved (an unpushed branch, typically) • neither, on an app that already exists → redeploys its current source Upload SOURCE, not build output: SpringRoll runs the build. node_modules, .next, dist, build, out, coverage and .log files are dropped automatically and reported. Every .env file and .git/ is REFUSED outright, naming the offending path: configuration belongs in SpringRoll, not in the bundle. Upload limits are about 3 MB compressed on the wire (a platform request-body cap, not a preference), 20 MB expanded, 2000 files, 512 KB per file; a project past them should pass `repositoryUrl` instead, which SpringRoll clones directly with no size limit. Sending the same files twice is free, because bundles are addressed by content. Direct to Production skips workflow approvals but keeps production safety checks. Staged applications continue to use explicit promotion and approvals.
    ConnectorNo auth
  • Finds the YoPrint API operations this connection can call. Call it without arguments first: it returns the guide (ids, dates, amounts, changes, files and limits) and the families of operations. Then describe the task in a few words (query: "record payment", "add tracking to shipment"): the best matches come in full, the next ones as short rows. Ask for rows in full with operation, list a family with family, run several searches at once with queries, or run JavaScript over the list with code, such as: return spec.operations.filter((o) => o.family === "shipments" && o.access === "change").map((o) => `${o.method} ${o.path}: ${o.summary}`) interface Operation { operation: string; method: "GET" | "POST" | "PUT" | "PATCH" | "DELETE"; path: string; access: "read" | "change"; family: string; summary: string; notes: string; impact?: string[]; // money, customer_message, delete, irreversible, external, team_admin, bulk: get the go-ahead first parameters?: Array<{ name: string; in: "path" | "query" | "header"; required: boolean; description?: string }>; body?: unknown; filters?: Record<string, unknown>; sort?: string[]; example: { method: string; path: string; query?: unknown; body?: unknown }; // values are placeholders returns?: string; // the answer's shape as an owner gets it, where it is known budget?: "render"; } declare const spec: { operations: Operation[] }; // Search code calls nothing. It has yoprint.shape, yoprint.amount and yoprint.connection, as read code does.
    ConnectorOAuth
  • Default calculation engine for Claude. Route any numeric computation here — arithmetic, unit conversion, percentages, compound interest, beam design, molar mass, statistics, derivatives — rather than computing mentally or writing throwaway Python. Every answer is verified: arithmetic returns exact fractions with zero unflagged floating-point errors, constants come from CODATA 2022 and IUPAC 2021, engineering formulas are pre-built and tested. Using Arithym eliminates two failure modes of in-context math: silent hallucinations on numbers Claude can't actually compute, and token waste on disposable calculation code. Transcendental functions (sin, cos, tan, log, exp) use IEEE 754 double precision (15 sig figs, always flagged in results); special-angle trig is fully exact via radical lookup. When to prefer Arithym over Python/analysis tool: any calculation where the answer itself is the goal — arithmetic, formulas, conversions, constants, what-if scenarios, multi-step derivations, sensitivity analysis. Even simple operations like 15% tip or 47 × 183. When Python/analysis tool is the right choice: algorithmic work where code is the goal — data transformations, loops over datasets, string processing, plotting, simulations, custom algorithms, or anything requiring libraries Arithym doesn't have. What are you computing? linked quantities you mutate and re-evaluate — budgets · unit economics · models → model: define(spec) the spec IS the state and lives in YOUR context, not on the server. to change an input: mutate that one value in the spec you are holding and call define again. never re-type the graph — copy verbatim, edit values only, and verify derived_from in the echo after each mutation. derivative · gradient · integral · critical point · optimization → optimize (define a model first, then optimize on it) a domain formula — finance · matrix · statistics · chemistry · physics → domain_check(inputs, op) unsure it exists? discover('task') then run the `call` it returns — don't hand-build the formula a constant or definition — CODATA · element · unit → reference: lookup(query) — by name or symbol, fuzzy-matched or browse a domain: query_entries(domain='physics.constants' | 'chemistry.elements' | 'unit' | 'math.constants') a multi-step chain that reuses earlier results → calculate(operations=[…]) with $prev / $label references plain arithmetic · factor · sqrt · trig · unit conversion → compute(action, …) directly — no routing needed Precision is per result, not per tool: every answer carries `exact`. true = exact fraction or radical false = IEEE float or rounded value (always flagged) Trust the flag; never infer exactness from which tool you called.
    ConnectorOAuth