Skip to content
Betav0.59.1
Works with your stack

Integrations

SpanDock works with the tools your teams already use: MCP connectors through the MCP gateway, and skills shared to every computer.

MCP connectors
142
skills
36
categories
25
MCP gateway

MCP connectors

Give your team's AI tools these services through the MCP gateway. An administrator adds a connector in a few clicks, with its sign-in and suggested permissions: read-only by default, with destructive tools needing approval. The MCP gateway is on the Premium and Enterprise plans.

Analytics & BI8 items

Automation1 item

Cloud & infrastructure15 items

Code and development11 items

Customer support7 items

Data & databases10 items

Design5 items

Documents & productivity19 items

E-commerce1 item

Finance & accounting9 items

Forms & surveys2 items

HR & recruiting7 items

Legal & contracts3 items

Marketing7 items

Meetings & communication9 items

Sales & CRM8 items

Security & compliance10 items

Work management10 items

Skills (beta)

Skills

Ready-made skills for your teams' AI tools, from engineering to sales, marketing, finance and legal. An administrator publishes them from the server dashboard, and every computer on the team gets them where its tools look for skills. The starter skills below are included in every plan; publishing your own skills is part of Premium and Enterprise.

Engineering16 items

  • Changelog

    changelog

    Draft release notes from the commits since the last tag, grouped into features, fixes and other changes, written for users. Use when preparing a release or asked what changed since the last version.

    Runs scriptsPlan: All plans

  • Code review

    code-review

    Review a code change for bugs, security problems and readability, and write clear, actionable review comments. Use when asked to review a diff, a pull request or recent changes.

    Plan: All plans

  • Commit messages

    commit-messages

    Write commit messages in the team's style: a short imperative subject and a body that explains why. Follows Conventional Commits when the repository uses it. Use when committing changes.

    Plan: All plans

  • Data handling

    data-handling

    Follow the company's rules on what may go into prompts, logs and test data: no customer personal data, credentials, secrets or confidential documents. Use whenever working with real data, logs, databases or customer content.

    Plan: All plans

  • Dependency audit

    dependency-audit

    Run the package manager's security audit and list the vulnerable dependencies with their severity and the version that fixes each. Use when asked about vulnerable packages, before a release, or after adding dependencies.

    Runs scriptsPlan: All plans

  • Dependency upgrade

    dependency-upgrade

    Upgrade a dependency safely: read the changelog for breaking changes, update the lockfile, fix call sites, run the tests, and keep it to one dependency per change. Use when asked to upgrade, bump or patch a package.

    Plan: All plans

  • Docs writer

    docs-writer

    Write and update documentation (READMEs, how-to guides, runbooks) in plain, task-focused language that matches the team's voice. Use when asked to document something or when a change makes existing docs wrong.

    Plan: All plans

  • Incident notes

    incident-notes

    Turn an outage or incident into short, blameless notes: impact, a timeline, root cause, and concrete follow-ups with owners. Use after an incident or when asked for a postmortem.

    Plan: All plans

  • Lint and format

    lint-format

    Run the repository's linters and formatters on the changed files only, and report or fix the problems. Use before committing, or when asked to lint or format.

    Runs scriptsPlan: All plans

  • Local environment

    local-environment

    Check that the tools and versions this repository needs are installed (language runtimes, package managers, databases, CLIs) and say exactly what's missing and how to install it. Use when setting up a machine, or when a build fails because of the environment.

    Runs scriptsPlan: All plans

  • Onboarding

    onboarding

    Explain how this repository is set up, built, tested and run, for a new team member or an agent starting work. Reads the repo and produces a short, accurate getting-started guide. Use when someone is new to the codebase or asks how to get started.

    Plan: All plans

  • Pull request writer

    pr-writer

    Write a clear pull request title and description from the current changes: what changed, why, how it was tested, and anything reviewers should check. Use when opening or updating a pull request.

    Plan: All plans

  • Run the tests

    run-tests

    Find and run this repository's tests, then summarise the failures with the file, the test and the likely cause. Use when asked to run the tests, check that a change works, or before saying a task is done.

    Runs scriptsPlan: All plans

  • Secret scan

    secret-scan

    Scan the current change for secrets (API keys, tokens, private keys, passwords) before it's committed, and stop if any are found. Use before committing or pushing, or when asked to check for leaked secrets.

    Runs scriptsPlan: All plans

  • Secure coding

    secure-coding

    Write and change code without introducing common security vulnerabilities: injection, secrets in code, unsafe deserialization, weak auth checks, risky dependencies. Use whenever writing code that handles user input, credentials, files, network or databases.

    Plan: All plans

  • Tests first

    tests-first

    Write or update tests together with every code change, run them, and only report the work as done when they pass. Use whenever implementing a feature or fixing a bug.

    Plan: All plans

Finance3 items

  • Investor update

    investor-update

    Draft a concise monthly or quarterly investor or board update with key metrics, highlights, lowlights, cash and runway, and specific asks, using only figures the person provides. Use when asked to write an investor update, a board update, a shareholder letter or a stakeholder progress report.

    Plan: All plans

  • Invoice check

    invoice-check

    Check supplier invoices before payment for duplicates, arithmetic errors, a match to the purchase order and delivery, required VAT or sales-tax fields, and fraud red flags such as changed bank details. Use when asked to check, review, approve or validate an invoice or a batch of invoices.

    Plan: All plans

  • Variance analysis

    variance-analysis

    Compare actuals against budget or forecast from a pasted table or a CSV or spreadsheet the person points to, compute variances and percentages, flag the material ones against a threshold the person can set, and frame the drivers as questions. Use when asked for a budget vs actual review, a variance analysis, month-end commentary or why spending is over or under plan.

    Plan: All plans

Legal2 items

  • Contract first pass

    contract-first-pass

    Do a first-pass review of a contract, NDA, MSA, order form or terms, summarising parties, term, renewal, termination, liability cap, indemnities, IP, confidentiality, data protection, governing law and payment terms, and flag unusual or one-sided clauses with quotes. Not legal advice. Use when asked to review, summarise or check a contract or agreement.

    Plan: All plans

  • Policy Q&A

    policy-qa

    Answer questions about the company's own policies and handbooks (travel, expenses, leave, security, data protection, code of conduct) strictly from the policy text, quoting the section, and saying clearly when the policy doesn't answer it. Use when asked what a policy says, whether something is allowed, or how a company rule applies.

    Plan: All plans

Marketing4 items

  • Campaign brief

    campaign-brief

    Turn a marketing idea into a one-page campaign brief with the objective, audience, key message, channels, deliverables, timeline, budget as given and how success is measured. Use when asked to plan a campaign, a launch, a promotion or to write a creative or marketing brief.

    Plan: All plans

  • Competitor analysis

    competitor-analysis

    Compare competitors fairly from sourced, public information, covering positioning, products, pricing as published, strengths, weaknesses and what it means for us. Use when asked for a competitor analysis, a comparison table, a battlecard or how we stack up against another company.

    Plan: All plans

  • SEO brief

    seo-brief

    Write an SEO content brief for a page or article, with the target query and search intent, an outline, the questions to answer, internal links and on-page details, written for readers rather than keyword stuffing. Use when asked for an SEO brief, a content brief, a blog outline for search, or how to rank a page.

    Plan: All plans

  • Social posts

    social-posts

    Write social media posts for LinkedIn, X, Instagram, Facebook, Threads or Bluesky from an announcement, article or idea, fitted to each network's length and tone, with variants to test. Use when asked to write social posts, a post thread, captions or to promote something on social media.

    Plan: All plans

Operations2 items

  • Meeting notes

    meeting-notes

    Turn a meeting transcript, recording summary or rough notes into clear minutes with the decisions made, action items with owners and due dates, open questions and a short summary. Use when asked to write up a meeting, summarise a call, produce minutes or extract action items.

    Plan: All plans

  • Status report

    status-report

    Write a weekly or monthly project or team status report with an overall RAG status, progress against milestones, risks and issues with owners, decisions needed and next steps, from notes, trackers or tickets. Use when asked for a status update, a progress report, a weekly update or a steering-committee summary.

    Plan: All plans

People3 items

  • Interview kit

    interview-kit

    Build a structured interview kit for a role, with the competencies to assess, behavioural and situational questions with follow-ups, a scoring rubric with anchored examples, and an interviewer guide for fair, consistent interviews. Use when asked to prepare interview questions, an interview plan, a scorecard or a hiring rubric.

    Plan: All plans

  • Job description

    job-description

    Write an inclusive, accurate job description with the role's purpose, responsibilities, must-have versus nice-to-have requirements, pay and benefits as given, and how to apply. Use when asked to write or improve a job description, a job ad or a role profile for hiring.

    Plan: All plans

  • Performance review

    performance-review

    Help a manager write a fair, evidence-based performance review or self-review from goals, examples and feedback, checking the wording for bias and vague language. Use when asked to write, edit or check a performance review, a self-assessment, annual review comments or feedback for an employee.

    Plan: All plans

Sales4 items

  • Account research

    account-research

    Build a short, sourced brief on a company or prospect before outreach or a meeting, covering what they do, recent news, likely priorities, who to talk to and open questions. Use when asked to research an account, a prospect, a customer or a company before a sales conversation.

    Plan: All plans

  • Call prep

    call-prep

    Prepare for a sales or customer call with a goal, an agenda, questions to ask, likely objections with honest answers, and the next step to aim for. Use when asked to prepare for a call, a meeting, a demo or a discovery conversation with a prospect or customer.

    Plan: All plans

  • Follow-up email

    follow-up-email

    Write a short follow-up email after a call or meeting that recaps what was agreed, lists next steps with owners and dates, and asks for one clear action. Use when asked to follow up with a prospect or customer, send a recap, or chase a reply.

    Plan: All plans

  • Proposal writer

    proposal-writer

    Draft a clear commercial proposal or statement of work from discovery notes, covering the customer's problem, the proposed solution, scope, timeline, pricing exactly as given, and next steps. Use when asked to write a proposal, a quote cover letter, an SOW or a pitch document for a customer.

    Plan: All plans

Support2 items

  • Knowledge-base article

    kb-article

    Write or update a help-centre or knowledge-base article from a resolved ticket, a product change or an engineer's notes, with a clear title, symptoms, steps and screenshots to capture. Use when asked to write a help article, a how-to, an FAQ entry, a troubleshooting guide or to turn a ticket into documentation.

    Plan: All plans

  • Support reply

    support-reply

    Draft an empathetic, accurate reply to a customer support ticket, chat or complaint that answers the question, follows the company's policies, asks for missing information and never promises what policy doesn't allow. Use when asked to reply to a customer, answer a ticket or handle a complaint.

    Plan: All plans

Missing a tool your team uses?

Tell us which one, and we'll look at adding it.

Contact us

Trademarks and logos belong to their owners; no endorsement implied. Logos from Simple Icons (opens in a new tab).

Cookie settings

Cookie categories

Details: Cookie Policy.