Permanently delete a project and its backend instance, including database and stored data. Confirm with user first and use specific ID to avoid accidental removal.
MIT
251,149 tools. Last updated 2026-06-30 11:30
"Connecting a backend project to an Elasticsearch database" matching MCP tools:
- Create an isolated Anythink backend instance with database, API, auth, and storage. Asynchronous provisioning returns project ID and API URL.MIT
- Generate a production-ready backend scaffold with Express or Next.js, including configurable auth, database, API docs, caching, and more.MIT
- Create a new database user with admin privileges for an existing MongoDB Atlas project to manage database access and permissions.MIT
- Monitor the health of your Digital Brain by checking backend status, database and vector index sizes, event counts, and LLM availability.MIT
- Retrieve complete project context in one call: brief, file tree, tasks, knowledge, failures, directives, agents, and policies. Use this first when connecting to a project.MIT
Matching MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to search, analyze, and interact with Elasticsearch through natural language.Last updated18Apache 2.0
- AlicenseBqualityAmaintenanceMCP server providing backend access to PostgreSQL, Storage (Supabase/S3), Iceberg data lake, and SQL seeds. It offers 32 tools for database queries, storage operations, seed management, and more.Last updated313MIT
Matching MCP Connectors
Cloudflare Workers MCP server: form-backend
Identify the project handle from an intake note
- Remove an Elasticsearch index and all its documents permanently to manage storage and maintain data organization.MIT
- Permanently remove an Elasticsearch index and all its documents by specifying the index name.MIT
- Remove specific documents from an Elasticsearch index by defining a query, managing conflicts, and controlling refresh behavior.MIT
- Remove metadata documentation for an Elasticsearch index to clean up index records and maintain data organization.MIT
- Create an Elasticsearch index with optional settings and mappings to define field types and index behavior.MIT
- Create or update an Elasticsearch index template to automatically apply settings, mappings, and aliases to new indices matching specified patterns.MIT
- Modify specific fields in an existing document within an Elasticsearch index by providing the index name, document ID, and updated content.MIT
- Modify documents in an Elasticsearch index using a query and script, handling conflicts and refresh options for controlled updates.MIT
- Search an Elasticsearch index using a query string to retrieve data from Elasticsearch clusters through the Model Context Protocol.
- Report the file-based memory backend status without any arguments. Returns status, backend type, and reason for the current state.MIT
- List projects in a billing account to get IDs, names, statuses, and API URLs. Use the ID to connect or delete a project.MIT
- List all services within a Bult project, including app, database, GitHub repository, Docker image, and cloud hosting deployment targets.MIT
- Automatically route journal entries to the correct project's database. Specify a project ID explicitly or let it auto-detect from context to log entries under the right project.AGPL 3.0
- Retrieve a safe, read-only summary of the Geond Agent Protocol MCP server to understand its purpose, version, environment variables, tool groups, setup hints, and example workflows before connecting to PostgreSQL.Apache 2.0