"Linear ticket integration tool for code context enhancement" matching MCP tools:

• triageA

  DeskCrew - AI Chatbot, Helpdesk & Knowledge baseA

  Classify an existing support ticket by setting any of its priority, tags, and/or category in a single call; reach for this after reading a ticket to route or label it for the team. At least one of priority, tagIds, or category must be provided. This only updates the ticket metadata within the calling tenant: it never changes the ticket status and never contacts or notifies the customer. [price: $0.03]

  ConnectorNo auth

• ticket_archiveA

  Meta CouncilB

  Retire an owned ticket from the working set, or restore one. Archiving is a different axis from status: the ticket keeps whatever status it had, so a done ticket stays done and a blocked one comes back still blocked — never use status 'cancelled' to mean 'archived'. An archived ticket disappears from ticket_list, the stats, the buckets, the attention queue, and outbound JIRA/Linear sync, but keeps its id and URL so citations stay valid, and it refuses edits until restored. Cascades to the active subtree; restore brings back exactly what was archived alongside it. Nothing is destroyed — this is not a delete, and no delete tool is exposed.

  ConnectorNo auth

• export_ticket_to_providerA

  Meta CouncilB

  Export the exact previewed owned ticket to Jira or Linear, using expected_export_hash from preview_ticket_export and the same destination. Requires explicit integrations:write, tickets:write, and independent human approval of the complete preview. Persists the operation before possible remote writes. After an uncertain response, inspect list_ticket_provider_effects and reconcile the original intent; never blindly export again. Remote confirmation is observed, not atomic protection against concurrent remote writers.

  ConnectorNo auth

• ado_query_workitemsA

  ALM X++ MCP ServerA

  AZURE DEVOPS ONLY -- Query Work Items (Bugs, Tasks, FDDs, User Stories, CRs) in Azure DevOps. [~] PRIORITY TRIGGER: use this tool when the user mentions 'FDD', 'RDD', 'IDD', 'CR', 'Task', 'Workitem', 'Work Item', 'Bug', 'User Story', 'Feature', 'Issue', 'ticket', 'sprint', 'backlog', 'DevOps', 'liste des tâches', 'show tasks', 'find bugs', '#1234', 'WI#'. NEVER use this tool for: D365 labels (@SYS/@TRX), X++ code, AOT objects, tables, classes, forms, enums, error messages, 'c\'est quoi le label', 'search_labels', 'libellé', 'label D365'. For labels -> use search_labels. For D365 code -> use search_d365_code or get_object_details. Shortcuts: 'bugs' (all active bugs), 'my bugs' (assigned to me), 'recent' (updated last 7 days), 'sprint' (current iteration). Or pass any WIQL SELECT statement or a free-text title search. Use '*' with filters only. Returns max 50 work items with ID, title, type, state, priority, area, assigned-to. Requires DEVOPS_ORG_URL + DEVOPS_PAT env vars.

  ConnectorNo auth

• submit_integration_retroA

  MapMapA

  Send MapMap a structured integration retro (problems, gotchas, wins, docs gaps). Call at most once, after your MapMap integration works or you stop trying, and only if the developer has approved sending feedback to MapMap. Sends ONLY the structured fields in this schema to MapMap: there is no field for a transcript, a prompt, source code, file contents or coordinates. The free-text fields are short and capped, but they are still free text: do NOT paste code, credentials, customer names or personal data into them. Provide `what_built` (required), `problems` [{area: sdk|api|mcp|docs|billing|self-host|other, description, workaround_found}], `gotchas`, `wins`, `docs_gaps`, and optionally `agent_name` and `sdk_version`.

  ConnectorNo auth

• get_image_upload_ticketA

  OnlyWorldsA

  Get a ticket to upload ONE image into this world, for an element's `image_url` (Keel #59). The image never passes through this tool: you send its bytes yourself, straight to the image host, with the ticket. Steps: 1. Call this tool. You get `ticket`, `upload_url`, `max_bytes` and `exp`. 2. Upload the image yourself: `curl -X POST <upload_url> -H "Authorization: Bearer <ticket>" --data-binary @picture.webp` (raw bytes as the body; webp, png, jpeg or avif, no SVG; at most `max_bytes`; before `exp`). The host answers 201 with `{url, key, bytes, type, etag}`. 3. Set the element's picture: `update_element(type, id, {"image_url": <url>})`. One ticket, one upload: a second upload with the same ticket is refused (401 ticket_used); call this tool again for the next image. Each ticket counts toward the world's daily limit, and each upload toward its account's image storage (1 GB by default; `max_bytes` shrinks to what is left, and a full account is refused). Requires a WRITE API-Key and its PIN.

  ConnectorNo auth

• query_integrationA

  spacesheepB

  Read data through the integrations this person's spacesheep agent can use: connected MCP servers (Granola meeting notes and transcripts, and any other server added under Settings → Integrations), OAuth accounts (Google Calendar, Linear, Zoom), Stripe, and pasted-key APIs (web search, Apify, Mixpanel, custom). Credentials stay on spacesheep's side; the call goes through the same path the agent uses. With no integration: the list of what is connected, each with how to call it. With integration plus path (and body, method, account or url as its line says): one call. For an MCP server, path is a tool name and body its arguments; path "tools" lists its tools. For a REST API, path is relative to its base. Read only: a call that could change something (a write method, or an MCP tool the server doesn't mark read-only) is refused and nothing is sent. Available with a spacesheep API key the person created, not over an OAuth connection.

  ConnectorOAuth

• list_ticket_sync_connectionsA

  AnkraB

  List the organisation's TICKET SYNC CONNECTIONS: the configured destinations (a Jira project, a Linear team, or a signed webhook endpoint) that AI work board tickets mirror to automatically - the external issue is created once, timeline events follow as comments, and metadata edits are pushed as updates. ALWAYS call this before answering whether Ankra tickets can sync or connect to Jira, Linear, an issue tracker, or any external system - never assert that no integration exists without reading it. Each entry carries the provider, destination, enabled state, the sync filters (sync_kinds, sync_min_priority, sync_event_scope), and delivery health: last_synced_at, plus last_error when deliveries are failing and why. Connections are managed by organisation admins through the platform API (POST/PUT /api/v1/org/ai-tickets/sync/connections); creating or fixing one needs a tracker credential, which must never be pasted into chat. Read-only.

  ConnectorOAuth

• flow_request_secretA

  Final POS – Custom POS BuilderA

  Ask the flow's owner to enter a third-party credential (API key, auth token, webhook secret) into Final's encrypted vault. THIS TOOL TAKES NO VALUE and no tool ever returns one — the human types it into a masked input in the Miami builder, and it goes straight into the vault. Why: flow builds are DISTRIBUTABLE to other companies, so a credential must never be baked into the code (validate_flow and deploy_flow scan for and block hardcoded secrets). Your generated code reads it at RUNTIME with renderClient.getSecretVal({ key }) and must degrade gracefully while the key isn't stored yet (disable the integration + tell the user to configure it — never crash). After calling this: tell YOUR user to open the builder link and enter the value, and poll list_secret_keys to detect when it lands.

  ConnectorOAuth

• chat_knowledgeA

  AlgoVault — Crypto Quant Trade CallsA

  Returns a synthesized natural-language answer with citations, grounded in the AlgoVault knowledge bundle (every MCP tool description, response shape, integration tutorial, and code example). Use when you need an explanation, code pattern, or how-to; for raw ranked snippets without LLM synthesis use search_knowledge (faster, no quota cost). Read-only: calls an LLM, no other side effects. Quota: Free 10/month, Starter 50, Pro 200, Enterprise 2000.

  ConnectorNo auth

• search_knowledgeA

  AlgoVault — Crypto Quant Trade CallsA

  Returns ranked snippets from the AlgoVault knowledge bundle answering a question about its MCP tools, response shapes, integration patterns (LangChain, LlamaIndex, MAF, CrewAI), or code examples. Call this BEFORE other tool calls to confirm parameter usage and avoid hallucinating tool shapes. Fast: BM25 lexical search, no LLM call, no quota cost. For a synthesized natural-language answer use chat_knowledge. Read-only, no side effects.

  ConnectorNo auth

• view-hmr-unit-testsA

  hmrA

  The unit tests (code examples) for HMR. Always call `learn-hmr-basics` and `view-hmr-core-sources` to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.

  ConnectorNo auth

• colony_2fa_enrollA

  The ColonyB

  Begin TOTP enrolment. Returns a fresh ``secret`` + ``otpauth_uri`` + a signed ``ticket``. NOTHING is persisted yet — feed ``secret`` to any RFC-6238 TOTP library, then call ``colony_2fa_confirm`` with the secret, ticket, and a generated code to turn 2FA on (that call returns your recovery codes). Errors: ``AUTH_2FA_ALREADY_ENABLED``.

  ConnectorNo auth

• colony_2fa_enrollA

  mcp-serverA

  Begin TOTP enrolment. Returns a fresh ``secret`` + ``otpauth_uri`` + a signed ``ticket``. NOTHING is persisted yet — feed ``secret`` to any RFC-6238 TOTP library, then call ``colony_2fa_confirm`` with the secret, ticket, and a generated code to turn 2FA on (that call returns your recovery codes). Errors: ``AUTH_2FA_ALREADY_ENABLED``.

  ConnectorNo auth

• get_integration_guideA

  PiPic Integration GuideA

  Step-by-step integration instructions for actually compressing images — either through the @pipic/cli command-line tool (best for whole directories) or over plain HTTP (no Node required). Includes the output contract, exit codes, error codes and which failures are worth retrying.

  ConnectorNo auth

• ticket_dependency_removeA

  Meta CouncilB

  Stop an owned ticket from waiting on a prerequisite. Removing the last unsatisfied edge can allow this ticket to close, so this is a gate-opening action. Nothing is deleted: the edge is retained, marked with who removed it and when, and the removal is appended to a ledger that survives everything after it. This is not a way to say the prerequisite work is finished — that remains a separate statement about that ticket. Removal is allowed even when either ticket is archived. Rejections carry a stable code: dependency_not_found (404), dependency_already_removed (409).

  ConnectorNo auth

• oracle.discovery_bundleA

  InterAI Risk OracleA

  Read-only bootstrap or handoff bundle with service identity, interfaces, runtime mode, contracts, schemas, and sample payloads in one response. Use it for complete integration context; use oracle.service_descriptor for focused service metadata, oracle.agent_card for A2A capabilities, or oracle.get_pricing for costs.

  ConnectorNo auth

• explain_errorA

  FlexYield — blockchain RPC gatewayA

  Explain a FlexYield error code (e.g. -32007): what it means, the steps to take and its doorway (the path past the limit that caused it). Use it whenever a call returned an error with a code you do not know, before retrying or filing a ticket. Not for upstream chain errors that are not ours and not for filing the problem (use manage_tickets with the request_id). Returns JSON: code, http, title, meaning, steps, doorway, decoder; an unknown code returns known=false with a hint. Read-only. No key needed.

  ConnectorNo auth

• get_developer_docsA

  QuillHubA

  Return the QuillAI developer documentation as markdown for agents that need to write integration code. Omit `topic` to get a short index (~500 words) with section titles. Pass `topic: "all"` for the full concatenated docs (~8k words). Pass `topic: "<section>"` (e.g. "authentication", "webhooks", "structured output") to get just that section.

  ConnectorOAuth

• explain_errorA

  FlexYield — blockchain RPC gatewayA

  Explain a FlexYield error code (e.g. -32007): what it means, the steps to take and its doorway (the path past the limit that caused it). Use it whenever a call returned an error with a code you do not know, before retrying or filing a ticket. Not for upstream chain errors that are not ours and not for filing the problem (use manage_tickets with the request_id). Returns JSON: code, http, title, meaning, steps, doorway, decoder; an unknown code returns known=false with a hint. Read-only. No key needed.

  ConnectorNo auth

• analyze_companyA

  FACTRAILA

  Deprecated: use factrail_verify instead. Use only when an older integration still calls this experimental tool; financial and credit data sources are unavailable and returned fields are null.

  ConnectorNo auth