Skip to main content
Glama
685,760 tools. Updated 2026-10-23 00:56

"Non-Docker Implementation of Jira with MCP" matching MCP tools:

  • Search a registry for packages matching q. registry=all fans out to npm, Docker Hub, and the VS Code Marketplace and merges the results. PyPI has no public search API, so registry=pypi returns 400 not_supported — look a PyPI package up by name via get_package instead. Results are normalized PackageSummary items (npm adds a relevance score; Docker adds isOfficial).
    ConnectorNo auth
  • Submits an enquiry to AI Implementation Cost — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Send my contact details to up to three AI implementation and marketing agencies, chosen by AI Implementation Cost, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."
    ConnectorNo auth
  • Search a project's own Jira (see get_linked_jira_issue) with JQL, as its own search does — e.g. 'project = ACME AND status != Done ORDER BY updated DESC', 'text ~ "login"'; currentUser() is the project token's owner, not you. Answers each issue's jira_key, jira_url, summary, type, status, priority, assignee and when it changed; read one whole with get_linked_jira_issue. A query the site cannot read comes back with its reason. This is the other site's JQL; this tracker's own issues are searched with search_issues. Name the project by 'project', or an issue here by 'issue'. For the people who work in the project; at most 10 reads of the linked Jira a minute per person.
    ConnectorNo auth
  • YA 2026 Singapore tax for residents, non-resident employees, and non-resident directors — including personal reliefs. Singapore tax depends first on residency. Residents use progressive rates up to 24% after eligible personal reliefs; non-resident employees pay the higher of 15% of employment income or the resident-rate calculation, while non-resident directors and most other non-resident income are taxed at 24%. This calculator runs the correct branch instead of silently assuming everyone is resident.
    ConnectorNo auth
  • Search and filter the WEO event corpus by `query` text or classification (bloc, tier, domain, event type, primary industry tag); returns the matching events with their metadata, capped by `limit` (default 20, max 50). Use to discover or shortlist events; for a single event's complete record, use `get_event`. Events enter after a verification lag from their implementation date (six months; 60 days for verified product releases), so recent events may not yet appear, and an empty result is not evidence that no such event has occurred. Free tier returns the classification facts with the deeper assessment and evidence withheld on non-sample events; full tier — and sample events on either tier — return every field.
    ConnectorNo auth
  • Search the registry by words: components, conventions, AI instruction sets and releases. Start here when you do not know the exact name of what you want. A component hit with `rustCrate` has a Mzizi Roots (Rust) implementation, which is the lead; at an equal score it ranks first. Documentation pages are searched by the docs_* tools.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Jira MCP Pack

  • Does that Docker tag actually exist? Real tags, sizes and platforms, live from Docker Hub.

  • Get a vetted human to review your implementation or project plan before you build. Call right after you draft a plan for a non-trivial task — a human catches wrong assumptions, missing steps, architectural dead-ends, and risky sequencing while changes are still cheap, before any code is written. Pass the plan, the goal it serves, and any constraints. Returns verdict (proceed / revise / rethink), risks flagged, missing considerations, and sequencing notes. Approved plans receive a Taste content certificate on-chain.
    ConnectorNo auth
  • Get a vetted human to review your implementation or project plan before you build. Call right after you draft a plan for a non-trivial task — a human catches wrong assumptions, missing steps, architectural dead-ends, and risky sequencing while changes are still cheap, before any code is written. Pass the plan, the goal it serves, and any constraints. Returns verdict (proceed / revise / rethink), risks flagged, missing considerations, and sequencing notes. Approved plans receive a Taste content certificate on-chain.
    ConnectorNo auth
  • Read the current public Wiplash karma prices, registration allowance, feedback settlement rules, and Cabana costs. Internal endpoints and implementation details are omitted.
    ConnectorNo auth
  • Full normalized details for one package by registry + name, in a single unified Package shape across npm, PyPI, Docker Hub, and the VS Code Marketplace. name handles scoped npm ids (e.g. @types/node), Docker namespaces (e.g. library/nginx or a bare nginx for official images), and VS Code publisher.extension ids. With registry=all the request fans out to every registry in parallel and returns a packages array (missing registries are silently dropped); otherwise a single package is returned.
    ConnectorNo auth
  • Every field of the AI Implementation Cost enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.
    ConnectorNo auth
  • Contract-level due diligence for an EVM contract address: whether the source is verified and through which route (sourcify / verifier-alliance / eth-bytecode-db), fully vs partially verified, whether the deployed bytecode still matches the verified source, proxy pattern and implementation address, deployer address and creation tx, contract age, and a capability scan of the verified source (and of the proxy implementation) for mint, pause, blacklist, selfdestruct and delegatecall. Returns markdown ending in a **Verdict** line. Up to 5 comma-separated addresses per call. $0.1 USDC for a single contract address, $0.25 for a 2-5 address batch, on Base (x402 v2, no account, no API key). An unpaid call answers HTTP 402 with the payment challenge; sign it and retry with the payment in the call `_meta`. Read-only: it never signs, transfers, or approves anything on the caller's behalf.
    ConnectorNo auth
  • Record completed repository implementation in one boundary call. Replaces the Work description with the factual implementedSummary and marks it done. If this closes the batch, batchSummary closes it in the same call; otherwise the response asks only for that missing summary. Calling it again on a done Work with batchSummary closes a Batch left open. A Work left planned or in progress inside a ready Batch is finished here too. Use it once implementation is complete.
    Connector
    Destructive
    No auth
  • Returns a window of lines from one text file on a server, with the total line count. Parameters: vpsId or hostname, provide at least one; path (absolute, under the readable roots); optional startLine (default 1) and maxLines (1-2000, default 400). Credential files (.env, private keys, keystores, password and database files, .vault-token), credential directories (including .ssh, .gnupg, .aws, .docker, .kube, .azure, .config/gcloud, /var/run/secrets, /run/secrets, /etc/ssl/private) and non-text files are refused. Call it to read a configuration or a source file the logs pointed at.
    ConnectorOAuth
  • List Worthune's Concordance-tested financial calculation models (an independent second implementation must agree with the engine, per the published spec). Returns model names and spec versions. Call get_model_contract before running a model.
    ConnectorNo auth
  • Fetch a single Jira issue by key (e.g. "ACME-123"). Returns key, browse URL, summary, description, issue type, status, priority, assignee, reporter, labels, project, timestamps, `acceptanceCriteria` (plain text, one line per item; null when the instance has no Acceptance Criteria field or it is empty), and `links` (URLs from the description and the issue's web links, deduped; each has a `kind` — "figma" marks a design mockup). TIP: links with kind 'figma' are design mockups — open them with figma_frame_image / figma_frame_spec to check the build against the design. Uses the calling user's stored Jira credential — does not accept inline credentials. Returns an actionable error if Jira is not configured.
    ConnectorOAuth
  • List the tags pushed for one image in this organization's Edgegap container registry, with push time and size. Call it after docker push to confirm the tag landed before edgegap_create_app_version, which otherwise fails later with an image-pull error.
    ConnectorAPI key
  • From a pull request back to the design(s) it implements: every design you can read whose implementation record or links name `pr`, with the implementation status and revision. Then call ui_builder_implementation_status for what the design expects.
    ConnectorNo auth
  • List non-secret private registry credential metadata for one owned service, including Docker Hub, GHCR, and exact custom HTTPS registry hostnames. Token values, encrypted envelopes, fingerprints, and key versions are never returned. Registry token creation and rotation are intentionally unavailable through MCP; use the VPSnet panel or direct REST API so the token does not enter model context. Requires applications:read.
    ConnectorOAuth
  • Get Docker registry login credentials and step-by-step instructions for pushing custom images. The password is the caller's own API token (read_write keys only); it works with docker/podman/skopeo login and in CI. Images pushed as <registry>/<app-name>:<tag> are automatically scoped to this account; reference them in create_custom_app as '<app-name>:<tag>' with is_custom true.
    ConnectorAPI key