Curated · community-readyReviewed 2026-07-13

Find the right free tool for every layer of your stack.

A curated directory for development, DevOps, IT, security, data, design, productivity and business operations. Every service includes official links, searchable tags, verification metadata, credential guidance and a copyable agent-access prompt.

The directory is also a real-world example of a production-ready $0 starting stack, built with Next.js, Vercel and Supabase-friendly architecture.

Explore all services ↓Open My Stack →Read the docs →Test API keys →

466

services and tools

practical categories

audience profiles

secure live key checks

DevOps

CI/CD, containers, infrastructure, observability and platform engineering.

Asset management, backups, networking, remote access and homelab operations.

Productivity

Notes, project management, documents, scheduling and collaboration.

Data & AI

Models, vector search, data pipelines, BI and analytics tooling.

The directory

Find the right building block

Free-tier limits and eligibility change. Verify current allowances, commercial-use terms and official agent tooling in each provider’s documentation before production use.

Search services, capabilities and tags

Sort results

466 of 466 services

✉

Free tier

Email & Messaging

Ably

Realtime pub/sub, presence and messaging infrastructure.

DevelopersBusiness & Operations

A permanent free plan is available, with product-specific quotas.

+1 tags

Audience: Developers · Business & Operations
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Ably using provider-maintained tooling only.

Service context:
- Category: Email & Messaging
- Intended audiences: Developers, Business & Operations
- Free model: Free tier
- Capabilities: realtime, pubsub, websocket, email-and-messaging, free-tier, developers, business-and-operations, agent-ready
- Official documentation: https://ably.com/docs
- Account or setup page: https://ably.com/sign-up

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Ably CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

⌖

Free tierLive key test

Maps & Data APIs

Abstract API

Email, phone, IP, VAT and utility APIs.

DevelopersData & AI

A permanent free plan is available, with product-specific quotas.

+2 tags

Audience: Developers · Data & AI
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Abstract API using provider-maintained tooling only.

Service context:
- Category: Maps & Data APIs
- Intended audiences: Developers, Data & AI
- Free model: Free tier
- Capabilities: email, phone, utility, maps-and-data-apis, free-tier, developers, data-and-ai, agent-ready, live-key-test
- Official documentation: https://docs.abstractapi.com
- Account or setup page: https://app.abstractapi.com/users/signup

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Abstract API CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

◆

Free tierLive key test

Security

AbuseIPDB

IP reputation and abuse-reporting API.

DevelopersSecurityDevOpsIT

A permanent free plan is available, with product-specific quotas.

+2 tags

Audience: Developers · Security +2
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to AbuseIPDB using provider-maintained tooling only.

Service context:
- Category: Security
- Intended audiences: Developers, Security, DevOps, IT
- Free model: Free tier
- Capabilities: ip, reputation, security, free-tier, developers, devops, it, agent-ready, live-key-test
- Official documentation: https://docs.abuseipdb.com
- Account or setup page: https://www.abuseipdb.com/register

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official AbuseIPDB CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

A11Y

Open source

Accessibility

Accessibility Insights

Accessibility testing tools from Microsoft.

DevelopersDesigners

Free to download or self-host under an open-source license.

+1 tags

Audience: Developers · Designers
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Accessibility Insights using provider-maintained tooling only.

Service context:
- Category: Accessibility
- Intended audiences: Developers, Designers
- Free model: Open source
- Capabilities: a11y, microsoft, testing, accessibility, open-source, developers, designers, agent-ready
- Official documentation: https://accessibilityinsights.io/docs/
- Account or setup page: https://accessibilityinsights.io/downloads/

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Accessibility Insights CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Setup guide

Open source

CI/CD & Delivery

act

Run GitHub Actions workflows locally in Docker containers.

DevelopersDevOps

Free to download or self-host under an open-source license.

+2 tags

Audience: Developers · DevOps
Last verified: 2026-07-13
Platforms: linux, macos, windows
Deployment: local

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to act using provider-maintained tooling only.

Service context:
- Category: CI/CD & Delivery
- Intended audiences: Developers, DevOps
- Free model: Open source
- Capabilities: github actions, ci, local, docker, ci-cd-and-delivery, open-source, developers, devops, agent-ready
- Official documentation: https://nektosact.com/
- Account or setup page: https://nektosact.com/installation/index.html

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official act CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: wmariuss/awesome-devops ↗

Setup guide

↯

Open source

Automation & Forms

Activepieces

Open-source business automation and integrations.

DevelopersProductivityBusiness & Operations

Free to download or self-host under an open-source license.

+2 tags

Audience: Developers · Productivity +1
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Activepieces using provider-maintained tooling only.

Service context:
- Category: Automation & Forms
- Intended audiences: Developers, Productivity, Business & Operations
- Free model: Open source
- Capabilities: automation, self-host, integrations, automation-and-forms, open-source, developers, productivity, business-and-operations, agent-ready
- Official documentation: https://www.activepieces.com/docs
- Account or setup page: https://cloud.activepieces.com/sign-up

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Activepieces CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

NET

Open source

Networking & Remote Access

AdGuard Home

Network-wide DNS server with ad blocking and parental controls.

ITProductivitySecurityDevOps

Free to download or self-host under an open-source license.

+4 tags

Audience: IT · Productivity +2
Last verified: 2026-07-13
Platforms: linux, macos, windows
Deployment: self-hosted

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to AdGuard Home using provider-maintained tooling only.

Service context:
- Category: Networking & Remote Access
- Intended audiences: IT, Productivity, Security, DevOps
- Free model: Open source
- Capabilities: dns, privacy, ad blocking, parental controls, networking-and-remote-access, open-source, it, productivity, security, devops
- Official documentation: https://github.com/AdguardTeam/AdGuardHome/wiki
- Account or setup page: https://github.com/AdguardTeam/AdGuardHome/wiki/Getting-Started

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official AdGuard Home CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: awesome-selfhosted/awesome-selfhosted ↗

Setup guide

✦

Free tier

Design & Creative

Adobe Color

Color wheel, palette extraction and accessibility tools.

Designers

A permanent free plan is available, with product-specific quotas.

Audience: Designers
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Adobe Color using provider-maintained tooling only.

Service context:
- Category: Design & Creative
- Intended audiences: Designers
- Free model: Free tier
- Capabilities: color, palette, accessibility, design-and-creative, free-tier, designers, agent-ready
- Official documentation: https://helpx.adobe.com/creative-cloud/adobe-color.html
- Account or setup page: https://color.adobe.com

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Adobe Color CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Setup guide

✦

Free tier

Design & Creative

Adobe Express

Quick social graphics, video and document design.

Designers

A permanent free plan is available, with product-specific quotas.

Audience: Designers
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Adobe Express using provider-maintained tooling only.

Service context:
- Category: Design & Creative
- Intended audiences: Designers
- Free model: Free tier
- Capabilities: graphics, video, templates, design-and-creative, free-tier, designers, agent-ready
- Official documentation: https://helpx.adobe.com/express/
- Account or setup page: https://new.express.adobe.com

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Adobe Express CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Setup guide

Free tier

Data & BI

Airbyte

Data integration platform for moving data between APIs, databases and warehouses.

Data & AIDevelopersBusiness & Operations

A permanent free plan is available, with product-specific quotas.

+3 tags

Audience: Data & AI · Developers +1
Last verified: 2026-07-13
Platforms: linux
Deployment: self-hosted, cloud

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Airbyte using provider-maintained tooling only.

Service context:
- Category: Data & BI
- Intended audiences: Data & AI, Developers, Business & Operations
- Free model: Free tier
- Capabilities: etl, data integration, connectors, warehouse, data-and-bi, free-tier, data-and-ai, developers, business-and-operations, agent-ready
- Official documentation: https://docs.airbyte.com/
- Account or setup page: https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Airbyte CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: awesome-selfhosted/awesome-selfhosted ↗

Setup guide

</>

Free tierLive key test

Developer Tools

Airtable

Spreadsheet-database hybrid with APIs and automations.

DevelopersDesignersDevOpsData & AI

A permanent free plan is available, with product-specific quotas.

+4 tags

Audience: Developers · Designers +2
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Airtable using provider-maintained tooling only.

Service context:
- Category: Developer Tools
- Intended audiences: Developers, Designers, DevOps, Data & AI
- Free model: Free tier
- Capabilities: database, no-code, automation, developer-tools, free-tier, developers, designers, devops, data-and-ai, agent-ready
- Official documentation: https://airtable.com/developers/web/api/introduction
- Account or setup page: https://airtable.com/signup

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Airtable CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

⌕

Free tier

Search & Vector

Algolia

Hosted search and discovery APIs.

DevelopersData & AI

A permanent free plan is available, with product-specific quotas.

+1 tags

Audience: Developers · Data & AI
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Algolia using provider-maintained tooling only.

Service context:
- Category: Search & Vector
- Intended audiences: Developers, Data & AI
- Free model: Free tier
- Capabilities: search, recommendations, instant, search-and-vector, free-tier, developers, data-and-ai, agent-ready
- Official documentation: https://www.algolia.com/doc/
- Account or setup page: https://dashboard.algolia.com/users/sign_up

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Algolia CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

⌖

Free tierLive key test

Maps & Data APIs

Alpha Vantage

Stock, forex, crypto and technical indicator APIs.

DevelopersData & AI

A permanent free plan is available, with product-specific quotas.

+2 tags

Audience: Developers · Data & AI
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Alpha Vantage using provider-maintained tooling only.

Service context:
- Category: Maps & Data APIs
- Intended audiences: Developers, Data & AI
- Free model: Free tier
- Capabilities: stocks, forex, market, maps-and-data-apis, free-tier, developers, data-and-ai, agent-ready, live-key-test
- Official documentation: https://www.alphavantage.co/documentation/
- Account or setup page: https://www.alphavantage.co/support/#api-key

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Alpha Vantage CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

IaC

Open source

Infrastructure as Code

Ansible

Agentless configuration management, provisioning and application deployment.

DevOpsIT

Free to download or self-host under an open-source license.

+2 tags

Audience: DevOps · IT
Last verified: 2026-07-13
Platforms: linux, macos
Deployment: local, self-hosted

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Ansible using provider-maintained tooling only.

Service context:
- Category: Infrastructure as Code
- Intended audiences: DevOps, IT
- Free model: Open source
- Capabilities: configuration management, automation, ssh, provisioning, infrastructure-as-code, open-source, devops, it, agent-ready
- Official documentation: https://docs.ansible.com/
- Account or setup page: https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Ansible CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: awesome-foss/awesome-sysadmin ↗

Setup guide

Open source

Data & BI

Apache Airflow

Workflow orchestration platform for scheduled data pipelines.

Data & AIDevelopersBusiness & Operations

Free to download or self-host under an open-source license.

+3 tags

Audience: Data & AI · Developers +1
Last verified: 2026-07-13
Platforms: linux
Deployment: self-hosted, cloud

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Apache Airflow using provider-maintained tooling only.

Service context:
- Category: Data & BI
- Intended audiences: Data & AI, Developers, Business & Operations
- Free model: Open source
- Capabilities: data orchestration, pipelines, scheduler, python, data-and-bi, open-source, data-and-ai, developers, business-and-operations, agent-ready
- Official documentation: https://airflow.apache.org/docs/
- Account or setup page: https://airflow.apache.org/docs/apache-airflow/stable/installation/index.html

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Apache Airflow CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: awesome-selfhosted/awesome-selfhosted ↗

Setup guide

NET

Open source

Networking & Remote Access

Apache Guacamole

Clientless remote desktop gateway supporting RDP, VNC and SSH.

ITSecurityDevOps

Free to download or self-host under an open-source license.

+3 tags

Audience: IT · Security +1
Last verified: 2026-07-13
Platforms: linux
Deployment: self-hosted

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Apache Guacamole using provider-maintained tooling only.

Service context:
- Category: Networking & Remote Access
- Intended audiences: IT, Security, DevOps
- Free model: Open source
- Capabilities: remote desktop, rdp, vnc, ssh, networking-and-remote-access, open-source, it, security, devops, agent-ready
- Official documentation: https://guacamole.apache.org/doc/gug/
- Account or setup page: https://guacamole.apache.org/doc/gug/installing-guacamole.html

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Apache Guacamole CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: awesome-foss/awesome-sysadmin ↗

Setup guide

Open source

Data & BI

Apache Superset

Enterprise data exploration and visualization platform.

Data & AIBusiness & Operations

Free to download or self-host under an open-source license.

+2 tags

Audience: Data & AI · Business & Operations
Last verified: 2026-07-13
Platforms: linux
Deployment: self-hosted

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Apache Superset using provider-maintained tooling only.

Service context:
- Category: Data & BI
- Intended audiences: Data & AI, Business & Operations
- Free model: Open source
- Capabilities: bi, dashboards, analytics, visualization, data-and-bi, open-source, data-and-ai, business-and-operations, agent-ready
- Official documentation: https://superset.apache.org/docs/
- Account or setup page: https://superset.apache.org/docs/installation/installing-superset-using-docker-compose/

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Apache Superset CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: awesome-selfhosted/awesome-selfhosted ↗

Setup guide

DOC

Open source

Knowledge & Documentation

AppFlowy

Open-source workspace for notes, wikis, projects and databases.

ProductivityBusiness & OperationsData & AI

Free to download or self-host under an open-source license.

+3 tags

Audience: Productivity · Business & Operations +1
Last verified: 2026-07-13
Platforms: linux, macos, windows, mobile
Deployment: local, self-hosted, cloud

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to AppFlowy using provider-maintained tooling only.

Service context:
- Category: Knowledge & Documentation
- Intended audiences: Productivity, Business & Operations, Data & AI
- Free model: Open source
- Capabilities: notes, wiki, projects, database, knowledge-and-documentation, open-source, productivity, business-and-operations, data-and-ai, agent-ready
- Official documentation: https://docs.appflowy.io/
- Account or setup page: https://appflowy.com/download

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official AppFlowy CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: awesome-selfhosted/awesome-selfhosted ↗

Setup guide

↯

Open source

Automation & Forms

Appsmith

Open-source internal tool and admin app builder.

DevelopersProductivityBusiness & Operations

Free to download or self-host under an open-source license.

+2 tags

Audience: Developers · Productivity +1
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Appsmith using provider-maintained tooling only.

Service context:
- Category: Automation & Forms
- Intended audiences: Developers, Productivity, Business & Operations
- Free model: Open source
- Capabilities: internal tools, low-code, self-host, automation-and-forms, open-source, developers, productivity, business-and-operations, agent-ready
- Official documentation: https://docs.appsmith.com
- Account or setup page: https://app.appsmith.com/user/signup

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Appsmith CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

Open source

Database & Backend

Appwrite

Open-source backend with database, auth, storage and functions.

DevelopersData & AI

Free to download or self-host under an open-source license.

+1 tags

Audience: Developers · Data & AI
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Appwrite using provider-maintained tooling only.

Service context:
- Category: Database & Backend
- Intended audiences: Developers, Data & AI
- Free model: Open source
- Capabilities: baas, auth, database, database-and-backend, open-source, developers, data-and-ai, agent-ready
- Official documentation: https://appwrite.io/docs
- Account or setup page: https://cloud.appwrite.io/register

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Appwrite CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

Open source

CI/CD & Delivery

Argo CD

Declarative GitOps continuous delivery for Kubernetes.

DevelopersDevOps

Free to download or self-host under an open-source license.

+2 tags

Audience: Developers · DevOps
Last verified: 2026-07-13
Platforms: linux
Deployment: self-hosted, cloud

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Argo CD using provider-maintained tooling only.

Service context:
- Category: CI/CD & Delivery
- Intended audiences: Developers, DevOps
- Free model: Open source
- Capabilities: gitops, kubernetes, continuous delivery, deployment, ci-cd-and-delivery, open-source, developers, devops, agent-ready
- Official documentation: https://argo-cd.readthedocs.io/
- Account or setup page: https://argo-cd.readthedocs.io/en/stable/getting_started/

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Argo CD CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: wmariuss/awesome-devops ↗

Setup guide

Free creditsLive key test

AI & ML

AssemblyAI

Speech recognition and audio intelligence APIs.

DevelopersData & AI

Free starter credits or a trial are available; ongoing usage may be paid.

+2 tags

Audience: Developers · Data & AI
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Start free ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to AssemblyAI using provider-maintained tooling only.

Service context:
- Category: AI & ML
- Intended audiences: Developers, Data & AI
- Free model: Free credits
- Capabilities: speech, stt, audio, ai-and-ml, free-credits, developers, data-and-ai, agent-ready, live-key-test
- Official documentation: https://www.assemblyai.com/docs
- Account or setup page: https://www.assemblyai.com/dashboard/signup

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official AssemblyAI CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

Open source

CMS & Content

Astro Starlight

Documentation theme and toolkit for Astro.

DevelopersDesignersProductivityBusiness & Operations

Free to download or self-host under an open-source license.

+3 tags

Audience: Developers · Designers +2
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Astro Starlight using provider-maintained tooling only.

Service context:
- Category: CMS & Content
- Intended audiences: Developers, Designers, Productivity, Business & Operations
- Free model: Open source
- Capabilities: docs, astro, static, cms-and-content, open-source, developers, designers, productivity, business-and-operations, agent-ready
- Official documentation: https://starlight.astro.build/guides/
- Account or setup page: https://starlight.astro.build/getting-started/

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Astro Starlight CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Setup guide

IaC

Open source

Infrastructure as Code

Atlantis

Terraform and OpenTofu pull-request automation for teams.

DevOpsIT

Free to download or self-host under an open-source license.

+2 tags

Audience: DevOps · IT
Last verified: 2026-07-13
Platforms: linux
Deployment: self-hosted, cloud

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Atlantis using provider-maintained tooling only.

Service context:
- Category: Infrastructure as Code
- Intended audiences: DevOps, IT
- Free model: Open source
- Capabilities: terraform, opentofu, pull requests, automation, infrastructure-as-code, open-source, devops, it, agent-ready
- Official documentation: https://www.runatlantis.io/docs/
- Account or setup page: https://www.runatlantis.io/docs/deployment.html

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Atlantis CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: wmariuss/awesome-devops ↗

Setup guide

◉

Free tier

Observability & Analytics

Atlassian Statuspage

Hosted public status pages and incident communication.

DevelopersDesignersDevOpsITData & AI

A permanent free plan is available, with product-specific quotas.

+4 tags

Audience: Developers · Designers +3
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Atlassian Statuspage using provider-maintained tooling only.

Service context:
- Category: Observability & Analytics
- Intended audiences: Developers, Designers, DevOps, IT, Data & AI
- Free model: Free tier
- Capabilities: status, incidents, communication, observability-and-analytics, free-tier, developers, designers, devops, it, data-and-ai
- Official documentation: https://support.atlassian.com/statuspage/
- Account or setup page: https://www.atlassian.com/try/cloud/signup?bundle=statuspage

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Atlassian Statuspage CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Setup guide

Open source

Authentication

Auth.js

Authentication library for web applications.

DevelopersSecurity

Free to download or self-host under an open-source license.

+1 tags

Audience: Developers · Security
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Auth.js using provider-maintained tooling only.

Service context:
- Category: Authentication
- Intended audiences: Developers, Security
- Free model: Open source
- Capabilities: auth, oauth, typescript, authentication, open-source, developers, security, agent-ready
- Official documentation: https://authjs.dev/getting-started
- Account or setup page: https://authjs.dev/getting-started

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Auth.js CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Setup guide

Free tier

Authentication

Auth0

Identity platform with social login, MFA and enterprise options.

DevelopersSecurity

A permanent free plan is available, with product-specific quotas.

+1 tags

Audience: Developers · Security
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Auth0 using provider-maintained tooling only.

Service context:
- Category: Authentication
- Intended audiences: Developers, Security
- Free model: Free tier
- Capabilities: auth, oauth, oidc, authentication, free-tier, developers, security, agent-ready
- Official documentation: https://auth0.com/docs
- Account or setup page: https://auth0.com/signup

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Auth0 CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

▲

Free tier

Hosting & Deploy

AWS Amplify

Full-stack web and mobile hosting on AWS.

DevelopersDevOps

A permanent free plan is available, with product-specific quotas.

+1 tags

Audience: Developers · DevOps
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to AWS Amplify using provider-maintained tooling only.

Service context:
- Category: Hosting & Deploy
- Intended audiences: Developers, DevOps
- Free model: Free tier
- Capabilities: aws, hosting, mobile, hosting-and-deploy, free-tier, developers, devops, agent-ready
- Official documentation: https://docs.amplify.aws
- Account or setup page: https://portal.aws.amazon.com/billing/signup

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official AWS Amplify CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

A11Y

Open source

Accessibility

axe DevTools / axe-core

Automated accessibility testing engine and browser tools.

DevelopersDesigners

Free to download or self-host under an open-source license.

+1 tags

Audience: Developers · Designers
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to axe DevTools / axe-core using provider-maintained tooling only.

Service context:
- Category: Accessibility
- Intended audiences: Developers, Designers
- Free model: Open source
- Capabilities: a11y, testing, open source, accessibility, open-source, developers, designers, agent-ready
- Official documentation: https://github.com/dequelabs/axe-core
- Account or setup page: https://www.deque.com/axe/devtools/

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official axe DevTools / axe-core CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Setup guide

◉

Free tierLive key test

Observability & Analytics

Axiom

Serverless logs, events and analytics.

DevelopersDevOpsITData & AI

A permanent free plan is available, with product-specific quotas.

+4 tags

Audience: Developers · DevOps +2
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Axiom using provider-maintained tooling only.

Service context:
- Category: Observability & Analytics
- Intended audiences: Developers, DevOps, IT, Data & AI
- Free model: Free tier
- Capabilities: logs, events, analytics, observability-and-analytics, free-tier, developers, devops, it, data-and-ai, agent-ready
- Official documentation: https://axiom.co/docs
- Account or setup page: https://app.axiom.co/register

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Axiom CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

▲

Free tier

Hosting & Deploy

Azure Static Web Apps

Static hosting, serverless APIs and integrated authentication.

DevelopersDevOps

A permanent free plan is available, with product-specific quotas.

+1 tags

Audience: Developers · DevOps
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Azure Static Web Apps using provider-maintained tooling only.

Service context:
- Category: Hosting & Deploy
- Intended audiences: Developers, DevOps
- Free model: Free tier
- Capabilities: azure, static, functions, hosting-and-deploy, free-tier, developers, devops, agent-ready
- Official documentation: https://learn.microsoft.com/azure/static-web-apps/
- Account or setup page: https://azure.microsoft.com/free

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Azure Static Web Apps CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

◫

Free tier

Storage & Media

Backblaze B2

S3-compatible object storage and backup.

DevelopersDevOps

A permanent free plan is available, with product-specific quotas.

+1 tags

Audience: Developers · DevOps
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Backblaze B2 using provider-maintained tooling only.

Service context:
- Category: Storage & Media
- Intended audiences: Developers, DevOps
- Free model: Free tier
- Capabilities: object storage, s3, backup, storage-and-media, free-tier, developers, devops, agent-ready
- Official documentation: https://www.backblaze.com/docs/cloud-storage
- Account or setup page: https://secure.backblaze.com/user_signin.htm

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Backblaze B2 CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

Free tier

Database & Backend

Backendless

Visual backend platform with database, auth and APIs.

DevelopersData & AI

A permanent free plan is available, with product-specific quotas.

+1 tags

Audience: Developers · Data & AI
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Backendless using provider-maintained tooling only.

Service context:
- Category: Database & Backend
- Intended audiences: Developers, Data & AI
- Free model: Free tier
- Capabilities: baas, no-code, auth, database-and-backend, free-tier, developers, data-and-ai, agent-ready
- Official documentation: https://backendless.com/docs/
- Account or setup page: https://develop.backendless.com/registration

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Backendless CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

Open source

CI/CD & Delivery

Backstage

Open platform for building internal developer portals and service catalogs.

DevelopersDevOps

Free to download or self-host under an open-source license.

+2 tags

Audience: Developers · DevOps
Last verified: 2026-07-13
Platforms: linux, macos
Deployment: self-hosted

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Backstage using provider-maintained tooling only.

Service context:
- Category: CI/CD & Delivery
- Intended audiences: Developers, DevOps
- Free model: Open source
- Capabilities: developer portal, service catalog, platform engineering, plugins, ci-cd-and-delivery, open-source, developers, devops, agent-ready
- Official documentation: https://backstage.io/docs/
- Account or setup page: https://backstage.io/docs/getting-started/

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Backstage CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: wmariuss/awesome-devops ↗

Setup guide

↯

Open source

Automation & Forms

Baserow

Open-source no-code database and application platform.

DevelopersDesignersProductivityBusiness & OperationsData & AI

Free to download or self-host under an open-source license.

+4 tags

Audience: Developers · Designers +3
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Baserow using provider-maintained tooling only.

Service context:
- Category: Automation & Forms
- Intended audiences: Developers, Designers, Productivity, Business & Operations, Data & AI
- Free model: Open source
- Capabilities: no-code, database, self-host, automation-and-forms, open-source, developers, designers, productivity, business-and-operations, data-and-ai
- Official documentation: https://baserow.io/docs
- Account or setup page: https://baserow.io/signup

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Baserow CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

↯

Free tier

Automation & Forms

Basin

Form endpoints, spam filtering and integrations.

DevelopersDesignersProductivityBusiness & Operations

A permanent free plan is available, with product-specific quotas.

+3 tags

Audience: Developers · Designers +2
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Basin using provider-maintained tooling only.

Service context:
- Category: Automation & Forms
- Intended audiences: Developers, Designers, Productivity, Business & Operations
- Free model: Free tier
- Capabilities: forms, spam, webhooks, automation-and-forms, free-tier, developers, designers, productivity, business-and-operations, agent-ready
- Official documentation: https://usebasin.com/docs
- Account or setup page: https://usebasin.com/users/sign_up

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Basin CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

</>

Free tier

Developer Tools

Beeceptor

Mock APIs, webhooks and request inspection.

DevelopersDevOps

A permanent free plan is available, with product-specific quotas.

+1 tags

Audience: Developers · DevOps
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Beeceptor using provider-maintained tooling only.

Service context:
- Category: Developer Tools
- Intended audiences: Developers, DevOps
- Free model: Free tier
- Capabilities: mock, api, webhooks, developer-tools, free-tier, developers, devops, agent-ready
- Official documentation: https://beeceptor.com/docs
- Account or setup page: https://beeceptor.com/register

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Beeceptor CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

Open source

Authentication

Better Auth

Framework-agnostic TypeScript authentication library.

DevelopersSecurity

Free to download or self-host under an open-source license.

+1 tags

Audience: Developers · Security
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Better Auth using provider-maintained tooling only.

Service context:
- Category: Authentication
- Intended audiences: Developers, Security
- Free model: Open source
- Capabilities: auth, typescript, self-host, authentication, open-source, developers, security, agent-ready
- Official documentation: https://www.better-auth.com/docs
- Account or setup page: https://www.better-auth.com/docs/installation

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Better Auth CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Setup guide

◉

Free tier

Observability & Analytics

Better Stack

Logs, uptime monitoring, incidents and status pages.

DevelopersDevOpsITData & AI

A permanent free plan is available, with product-specific quotas.

+3 tags

Audience: Developers · DevOps +2
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Better Stack using provider-maintained tooling only.

Service context:
- Category: Observability & Analytics
- Intended audiences: Developers, DevOps, IT, Data & AI
- Free model: Free tier
- Capabilities: logs, uptime, status, observability-and-analytics, free-tier, developers, devops, it, data-and-ai, agent-ready
- Official documentation: https://betterstack.com/docs/
- Account or setup page: https://betterstack.com/users/sign-up

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Better Stack CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

</>

Free tier

Developer Tools

Bitbucket

Git repositories and pipelines for small teams.

DevelopersDevOps

A permanent free plan is available, with product-specific quotas.

+1 tags

Audience: Developers · DevOps
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Bitbucket using provider-maintained tooling only.

Service context:
- Category: Developer Tools
- Intended audiences: Developers, DevOps
- Free model: Free tier
- Capabilities: git, ci, atlassian, developer-tools, free-tier, developers, devops, agent-ready
- Official documentation: https://support.atlassian.com/bitbucket-cloud/
- Account or setup page: https://bitbucket.org/account/signup/

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Bitbucket CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

✦

Open source

Design & Creative

Blender

3D modeling, animation, rendering and video editing.

Designers

Free to download or self-host under an open-source license.

Audience: Designers
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Blender using provider-maintained tooling only.

Service context:
- Category: Design & Creative
- Intended audiences: Designers
- Free model: Open source
- Capabilities: 3d, animation, rendering, design-and-creative, open-source, designers, agent-ready
- Official documentation: https://docs.blender.org
- Account or setup page: https://www.blender.org/download/

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Blender CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Setup guide

DOC

Open source

Knowledge & Documentation

BookStack

Simple self-hosted platform for organizing documentation into books and pages.

ProductivityBusiness & Operations

Free to download or self-host under an open-source license.

+2 tags

Audience: Productivity · Business & Operations
Last verified: 2026-07-13
Platforms: linux
Deployment: self-hosted

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to BookStack using provider-maintained tooling only.

Service context:
- Category: Knowledge & Documentation
- Intended audiences: Productivity, Business & Operations
- Free model: Open source
- Capabilities: wiki, documentation, knowledge, self-host, knowledge-and-documentation, open-source, productivity, business-and-operations, agent-ready
- Official documentation: https://www.bookstackapp.com/docs/
- Account or setup page: https://www.bookstackapp.com/docs/admin/installation/

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official BookStack CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: awesome-selfhosted/awesome-selfhosted ↗

Setup guide

BKP

Open source

Backup & Recovery

BorgBackup

Deduplicating encrypted backup tool with compression and remote repositories.

ITDevOps

Free to download or self-host under an open-source license.

+2 tags

Audience: IT · DevOps
Last verified: 2026-07-13
Platforms: linux, macos
Deployment: local, self-hosted

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to BorgBackup using provider-maintained tooling only.

Service context:
- Category: Backup & Recovery
- Intended audiences: IT, DevOps
- Free model: Open source
- Capabilities: backup, encryption, deduplication, cli, backup-and-recovery, open-source, it, devops, agent-ready
- Official documentation: https://borgbackup.readthedocs.io/
- Account or setup page: https://borgbackup.readthedocs.io/en/stable/installation.html

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official BorgBackup CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: awesome-foss/awesome-sysadmin ↗

Setup guide

Free tier

AI & ML

Braintrust

Evaluation, prompts and observability for AI applications.

DevelopersData & AI

A permanent free plan is available, with product-specific quotas.

+1 tags

Audience: Developers · Data & AI
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Braintrust using provider-maintained tooling only.

Service context:
- Category: AI & ML
- Intended audiences: Developers, Data & AI
- Free model: Free tier
- Capabilities: llm, evaluation, prompts, ai-and-ml, free-tier, developers, data-and-ai, agent-ready
- Official documentation: https://www.braintrust.dev/docs
- Account or setup page: https://www.braintrust.dev/signup

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Braintrust CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

✉

Free tierLive key test

Email & Messaging

Brevo

Transactional email, campaigns, SMS and CRM.

DevelopersDesignersBusiness & Operations

A permanent free plan is available, with product-specific quotas.

+3 tags

Audience: Developers · Designers +1
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Brevo using provider-maintained tooling only.

Service context:
- Category: Email & Messaging
- Intended audiences: Developers, Designers, Business & Operations
- Free model: Free tier
- Capabilities: email, sms, crm, email-and-messaging, free-tier, developers, designers, business-and-operations, agent-ready, live-key-test
- Official documentation: https://developers.brevo.com
- Account or setup page: https://onboarding.brevo.com/account/register

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Brevo CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

✓

Free for OSS

Testing & QA

BrowserStack

Cross-browser and device testing with open-source plans.

DevelopersDevOps

Free usage is available for qualifying open-source projects.

+1 tags

Audience: Developers · DevOps
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to BrowserStack using provider-maintained tooling only.

Service context:
- Category: Testing & QA
- Intended audiences: Developers, DevOps
- Free model: Free for OSS
- Capabilities: browser, devices, testing, testing-and-qa, free-for-oss, developers, devops, agent-ready
- Official documentation: https://www.browserstack.com/docs
- Account or setup page: https://www.browserstack.com/users/sign_up

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official BrowserStack CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

</>

Open source

Developer Tools

Bruno

Git-friendly offline API client.

DevelopersDevOps

Free to download or self-host under an open-source license.

+1 tags

Audience: Developers · DevOps
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Get started ↗Official docs ↗

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Bruno using provider-maintained tooling only.

Service context:
- Category: Developer Tools
- Intended audiences: Developers, DevOps
- Free model: Open source
- Capabilities: api, git, offline, developer-tools, open-source, developers, devops, agent-ready
- Official documentation: https://docs.usebruno.com
- Account or setup page: https://www.usebruno.com/downloads

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Bruno CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Setup guide

↯

Free tier

Automation & Forms

Bubble

Visual full-stack web application builder.

DevelopersDesignersProductivityBusiness & Operations

A permanent free plan is available, with product-specific quotas.

+3 tags

Audience: Developers · Designers +2
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Bubble using provider-maintained tooling only.

Service context:
- Category: Automation & Forms
- Intended audiences: Developers, Designers, Productivity, Business & Operations
- Free model: Free tier
- Capabilities: no-code, apps, visual, automation-and-forms, free-tier, developers, designers, productivity, business-and-operations, agent-ready
- Official documentation: https://manual.bubble.io
- Account or setup page: https://bubble.io/signup

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Bubble CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup

Find the right free tool for every layer of your stack.

The directory is also a real-world example of a production-ready $0 starting stack, built with Next.js, Vercel and Supabase-friendly architecture.

⌖

Free tierLive key test

Maps & Data APIs

Abstract API

Email, phone, IP, VAT and utility APIs.

DevelopersData & AI

A permanent free plan is available, with product-specific quotas.

+2 tags

Audience: Developers · Data & AI
Last verified: 2026-07-13
Platforms: See official docs
Deployment: Provider-specific

Give an agent access

Copy this prompt into your coding agent. It requires official provider tooling and least-privileged credentials.

Configure agent access to Abstract API using provider-maintained tooling only.

Service context:
- Category: Maps & Data APIs
- Intended audiences: Developers, Data & AI
- Free model: Free tier
- Capabilities: email, phone, utility, maps-and-data-apis, free-tier, developers, data-and-ai, agent-ready, live-key-test
- Official documentation: https://docs.abstractapi.com
- Account or setup page: https://app.abstractapi.com/users/signup

Tasks:
1. Read the official documentation and identify the provider's verified organization, package namespace, binary, repository, and current installation instructions.
2. Check whether the provider maintains an official MCP server. If it does, install and configure that MCP server for the current agent runtime.
3. If no official MCP server exists, install the official Abstract API CLI using the provider's documented method. Prefer a project-scoped installation when supported; explain before installing globally or modifying system packages.
4. If the provider publishes neither an official MCP server nor an official CLI, use its official SDK or API and clearly state that no official MCP/CLI is available.
5. Verify package ownership and release provenance before installation. Do not use similarly named packages, third-party MCP servers, forks, install scripts, or binaries unless I explicitly approve them.
6. Authenticate with the least-privileged scopes required for read-only access first. Prefer OAuth, device login, short-lived credentials, or a platform secret store when supported.
7. Keep credentials out of chat, source control, shell history, logs, screenshots, and generated files. Never print or echo a secret.
8. Run a harmless read-only identity, account, list, version, or status command to verify the connection. Do not create, modify, deploy, delete, purchase, invite, or publish anything during verification.
9. Report:
   - the official package, binary, repository, publisher, and installed version
   - the exact installation and configuration commands used
   - the configuration files and environment-variable names added (never secret values)
   - the permissions or scopes granted
   - the verification command and sanitized result
   - any remaining manual action or security caveat

Stop and ask for approval if official ownership is unclear, installation requires elevated privileges, or the requested read-only connection cannot be achieved safely.

Source: yishaik/free-stack-starter ↗

Test setup