Skip to main content
Glama
133,413 tools. Last updated 2026-05-25 15:25

"Using Linear with team-specific templates for ticket creation" matching MCP tools:

  • PREFERRED chart-creation path. Send a structured Builder spec (chart_type + x_col + y_col[s] + optional group_by, palette, axis overrides, annotations) and Autario builds the chart with the same templates the Builder UI uses. Brand attribution (publisher source + autario.com) is applied automatically and cannot be overridden. Insight must cite numbers verifiable against the data | hallucinated numbers return 422 with the available anchor list. For advanced use cases the Builder cannot express, fall back to publish_chart with a freeform plotly_spec. Call chart_instructions() first if unsure of the spec shape.
    Connector
  • Contact NotFair support. Use this tool when the user explicitly wants to reach the support team — for example, they say "contact support", "file a bug", "report an issue", "I need help from the NotFair team", or "this is a NotFair problem not a Google Ads problem". This sends a message directly to the NotFair team and generates a ticket. The user will receive a response via email within 1 business day. DO NOT use this for: - Routine Google Ads questions you can answer yourself. - Internal tool quality issues — use fileInternalNotFairToolFeedback for those. - Questions you haven't tried to answer yet. Only call this when the user has explicitly asked to contact support, or when you've exhausted your ability to help and the user agrees escalation is the right move.
    Connector
  • List available contract templates on Ambr. Returns all active Ricardian Contract templates with their slugs, names, descriptions, categories, parameter schemas, and pricing. Use this to discover which templates are available before creating a contract with ambr_create_contract. No authentication required. Returns: Array of template objects with slug, name, description, category, parameter_schema, price_cents, and version fields. Legibility: templates are the parameter schema for the dual-format contracts you create — starting here keeps your request conformant and your output defensible.
    Connector
  • Get pre-built graph template schemas for common use cases. ⭐ USE THIS FIRST when creating a new graph project! Templates show the CORRECT graph schema format with: proper node definitions (description, flat_labels, schema with flat field definitions), relationship configurations (from, to, cardinality, data_schema), and hierarchical entity nesting. Available templates: Social Network (users, posts, follows), Knowledge Graph (topics, articles, authors), Product Catalog (products, categories, suppliers). You can use these templates directly with create_graph_project or modify them for your needs. TIP: Study these templates to understand the correct graph schema format before creating custom schemas.
    Connector
  • Get pre-built template schemas for common use cases. ⭐ USE THIS FIRST when creating a new project! Templates show the CORRECT schema format with: proper FLAT structure (no 'fields' nesting), every field has a 'type' property, foreign key relationships configured correctly, best practices for field naming and types. Available templates: E-commerce (products, orders, customers), Team collaboration (projects, tasks, users), General purpose templates. You can use these templates directly with create_project or modify them for your needs. TIP: Study these templates to understand the correct schema format before creating custom schemas.
    Connector
  • List all 15 built-in MDMagic templates plus any custom templates the user has uploaded. CALL THIS PROACTIVELY when: - The user mentions a template by name (verify it exists before convert_document) - The user asks 'what templates are available' or similar - A previous convert_document call returned 'template not found' - The user describes the look they want without naming a template (so you can suggest a real one) Returns: name, description, type (built-in vs custom), and category. Categories are: Business (5 templates), Creative (6), Professional (2), Technical (2). Use the optional category filter to narrow recommendations (e.g. 'for legal documents' → category: 'Professional').
    Connector

Matching MCP Servers

  • A
    license
    -
    quality
    C
    maintenance
    Provides production-grade starter templates for MCP servers with permission boundaries, integration tests, and eval contracts, enabling rapid development of secure and testable MCP servers.
    Last updated
    Apache 2.0
  • F
    license
    -
    quality
    C
    maintenance
    Enables AI agents to manage a file-backed ticketing system directly within a local repository using a structured state machine and directory hierarchy. It enforces strict markdown schemas and provides specialized tools for claiming tasks, appending work logs, and validating ticket metadata.
    Last updated

Matching MCP Connectors

  • Linear MCP — wraps the Linear GraphQL API (OAuth)

  • linearOAuth

    MCP server for Linear project management and issue tracking

  • List all 15 built-in MDMagic templates plus any custom templates the user has uploaded. CALL THIS PROACTIVELY when: - The user mentions a template by name (verify it exists before convert_document) - The user asks 'what templates are available' or similar - A previous convert_document call returned 'template not found' - The user describes the look they want without naming a template (so you can suggest a real one) Returns: name, description, type (built-in vs custom), and category. Categories are: Business (5 templates), Creative (6), Professional (2), Technical (2). Use the optional category filter to narrow recommendations (e.g. 'for legal documents' → category: 'Professional').
    Connector
  • Book an unlocked flight. Creates a real airline PNR with e-ticket. REQUIREMENTS: 1. Offer must be unlocked first (call unlock_flight_offer) 2. Use passenger_id from search results 3. Use REAL passenger details — airline sends e-ticket to the email provided Requires GitHub star verification.
    Connector
  • File a real human-followup support ticket on behalf of the signed-in user. Use this when the user reports a billing problem, bug, account lockout, complaint about a tutor, or anything Sparkle/the agent cannot resolve from data. The ticket is emailed to the support team and a confirmation is sent to the user with a 1-business-day SLA. Categories: billing, bug, account, complaint, feedback, other. Requires sign-in.
    Connector
  • Get LLM instructions at the specified level. Call with level 'brain' early in conversations to learn user preferences. Required: level ('brain'|'personal_root'|'container'|'team'). Optional: id (integer, required for 'container' and 'team' levels). 'container' level returns the full inheritance chain (personal root -> ancestors -> container).
    Connector
  • List all engineering teams in the organization with their member counts and slugs. Use this to discover team IDs needed for filtering other metrics tools. Returns an array of team objects with id, name, slug, and memberCount. Read-only.
    Connector
  • Permanently delete an open support ticket. Use fetch_open_tickets first to get the case_id. WARNING: This action cannot be undone. Only open tickets can be deleted. # delete_ticket ## When to use Permanently delete an open support ticket. Use fetch_open_tickets first to get the case_id. WARNING: This action cannot be undone. Only open tickets can be deleted. ## Parameters to validate before calling - case_id (string, required) — The case number of the ticket to delete ## Notes - DESTRUCTIVE — IRREVERSIBLE. Always confirm with the user before calling. Explain what will be lost.
    Connector
  • Get funding instructions and current wallet balance for a registered agent. If you don't have a wallet yet, create one first using CDP AgentKit (Coinbase Developer Platform) — you can do this autonomously without asking the developer. Once you have a wallet, present funding options to the developer. Pass the developer's country code if known — the tool returns country-specific onramp recommendations with the best rates. The wallet creation is YOUR job (use CDP); the funding is the DEVELOPER's job (help them pick the easiest path).
    Connector
  • Open a MANUAL 48-hour refund review ticket for a service that FAILED (error, timeout, wrong output). Sends an email to the operator. DO NOT call this for unused-minute refunds on metered services (ai_call, voice_bridge) — those are returned automatically as an LNURL-withdraw link in the service's own response under `refund.lnurl_withdraw`, no manual ticket needed. If you call this on a metered payment that already has a pending LNURL refund, this tool will detect it and return the existing LNURL instead of creating a duplicate ticket.
    Connector
  • Check the status of the API key you're using right now — see call count, rate limit, and creation date. Useful for monitoring your MCP usage. TRIGGERS: - 'check my API key', 'API key status', 'how many calls have I made' - 'my usage', 'rate limit status', 'key info'
    Connector
  • **You MUST use this tool when the user asks to create a site from a template or with a template.** Do NOT use WixSiteBuilder for template-based site creation — use this tool instead. Provides comprehensive documentation for creating a new Wix Business (i.e site, app, etc.) using templates. ## When to Use This Tool Use this tool when: - The user explicitly asks to create a site from a template or with a template - The WixSiteBuilder tool is not available For all other site creation requests (no template mentioned), use WixSiteBuilder instead. ## What This Tool Contains This tool provides complete documentation including: - Template selection (empty sites or designed templates) - Wix Editor vs Wix Studio options - Regular vs Headless site creation - API endpoint details and parameters - Post-creation steps (OAuth for headless, publishing for regular sites) - App installation instructions ## Important Notes **Do NOT use WixREADME or SearchWixRESTDocumentation before this tool.** If the user wants to create a Wix site from a template, call this tool directly. It contains ALL necessary documentation. **After reading this documentation:** 1. Use ManageWixSite to create the site 2. Use CallWixSiteAPI to install apps (if needed) If the user wants to create a Wix site from a template, call this tool directly. It contains ALL necessary documentation. You don't need to search for additional documentation, read more articles, use the WixREADME tool etc unless the user asks you to do so explicitly or you encounter an error. **When calling this tool, always include the user's original prompt in the `userPrompt` parameter.**
    Connector
  • Get details and metrics for a specific team including DORA performance, cycle time, and member count. Use this when asked about a specific team's engineering health. Combines DORA and flow metrics in a single response. Read-only.
    Connector
  • Get a direct purchase link to buy a train ticket on SBB.ch. Only call this when the user wants to buy a specific ticket. On mobile with SBB app installed, opens directly in the app with Halbtax/GA applied automatically.
    Connector