Chroma’s official MCP server: vector search and collection management for RAG workflows.
Nothing to run from here
Appbase is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
trust score
4
downloads a day
local
runs on your machine
297
downloads in 30d
What it does
Supabase projects, tables, SQL, migrations, and storage from your MCP client.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user appbase-mcp '--' npx -y @reneturcios/appbase mcp
# 2 — ask your agent for something these tools do
# list_tables, list_extensions, list_migrations and 25 more
Appbase costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CLAll 381 servers
CloudCorpRecords381 servers
28 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Appbase as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user appbase-mcp '--' npx -y @reneturcios/appbase mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
28 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Lists all tables within the specified schemas.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose tables are listed. |
| schemas | array | no | The database schemas to list tables from, defaulting to public when omitted. |
Lists all extensions in the database.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose database extensions are listed. |
Lists all migrations in the database.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose migrations are listed. |
Executes raw SQL in the database.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project to run the SQL against. |
| query | string | yes | The raw SQL query to execute in the project's database. |
Applies a SQL migration to the database. SQL passed to this tool will be tracked within the database, so use this for DDL operations (schema changes).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project to apply the migration to. |
| name | string | yes | The name of the migration to record in the database. |
| query | string | yes | The SQL statements of the migration to apply. |
Gets logs for a Supabase project by service (api, postgres, edge-function, auth, storage, realtime, or branch-action).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose logs are retrieved. |
| service | string | yes | The service to get logs for, one of api, postgres, edge-function, auth, storage, realtime, or branch-action. |
Gets advisory notices for a Supabase project, by type: security or performance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose advisors are retrieved. |
| type | string | yes | The type of advisory notices to get, either security or performance. |
Gets the API URL for a Supabase project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose API URL is returned. |
Gets the publishable and anon API keys for a Supabase project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose publishable and anon API keys are returned. |
Generates TypeScript types based on the database schema.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project to generate TypeScript types for. |
| included_schemas | array | no | The database schemas to include when generating the TypeScript types. |
Lists all Edge Functions in a Supabase project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose Edge Functions are listed. |
Gets details for an Edge Function by slug.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project that owns the Edge Function. |
| function_slug | string | yes | The slug of the Edge Function to retrieve. |
Deploys an Edge Function to a Supabase project from inline files.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project to deploy the Edge Function to. |
| name | string | yes | The name of the Edge Function to deploy. |
| files | array | yes | The inline files that make up the Edge Function, each with a name and content. |
| entrypoint_path | string | no | The path of the entrypoint file for the Edge Function. |
| import_map_path | string | no | The path of the import map file for the Edge Function. |
Lists all storage buckets in a Supabase project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose storage buckets are listed. |
Creates a new storage bucket in a Supabase project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project to create the storage bucket in. |
| name | string | yes | The name of the new storage bucket. |
| public | boolean | no | Whether the new storage bucket is publicly accessible. |
| file_size_limit | number | no | The maximum file size allowed for uploads to the bucket. |
| allowed_mime_types | array | no | The MIME types allowed for files uploaded to the bucket. |
Lists all development branches for a Supabase project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project whose development branches are listed. |
Creates a new development branch for a Supabase project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project to create the development branch in. |
| name | string | yes | The name of the new development branch. |
| confirm_cost_id | string | no | The cost confirmation ID authorizing the branch creation charge, if one was obtained. |
Deletes a development branch from a Supabase project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project that owns the development branch. |
| branch_id | string | yes | The ID of the development branch to delete. |
Merges migrations and edge functions from a development branch into production.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project that owns the development branch. |
| branch_id | string | yes | The ID of the development branch to merge into production. |
Resets a development branch to its parent state, optionally at a migration version.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project that owns the development branch. |
| branch_id | string | yes | The ID of the development branch to reset. |
| migration_version | string | no | The optional migration version to reset the branch to. |
Rebases a development branch on its parent, applying newer migrations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project that owns the development branch. |
| branch_id | string | yes | The ID of the development branch to rebase on its parent. |
Lists all Supabase projects for the user.
No parameter schema on file.
Gets details for a project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The ID of the project to retrieve details for. |
Creates a new Supabase project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The name of the new Supabase project. |
| organization_id | string | yes | The ID of the organization to create the new project in. |
| region | string | no | The region to create the new project in. |
| confirm_cost_id | string | no | The cost confirmation ID authorizing the project creation charge, if one was obtained. |
Pauses a project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project to pause. |
Restores a project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The reference ID of the Supabase project to restore. |
Lists all organizations that the user is a member of.
No parameter schema on file.
Gets details for an organization.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The ID of the organization to retrieve details for. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Appbase or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 96 / 100
Release 0.1.0 · scanned 2 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest9bdaf77224e4ad2261b54e3b7ab18093f9fb546261d9e45861a9e31b890cb156
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (28 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_tables | no tags | |
| list_extensions | no tags | |
| list_migrations | no tags | |
| execute_sql | sensitive-source | sensitive-source: keyword "execute_sql" |
| apply_migration | no tags | |
| get_logs | sensitive-source | sensitive-source: keyword "get_logs" |
| get_advisors | no tags | |
| get_project_url | no tags | |
| get_publishable_keys | no tags | |
| generate_typescript_types | no tags | |
| list_edge_functions | no tags | |
| get_edge_function | no tags | |
| deploy_edge_function | no tags | |
| list_storage_buckets | no tags | |
| create_storage_bucket | no tags | |
| list_branches | no tags | |
| create_branch | no tags | |
| delete_branch | no tags | |
| merge_branch | no tags | |
| reset_branch | no tags | |
| rebase_branch | no tags | |
| list_projects | no tags | |
| get_project | no tags | |
| create_project | no tags | |
| pause_project | no tags | |
| restore_project | no tags | |
| list_organizations | no tags | |
| get_organization | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest9bdaf77224e4ad22
Scanned2026-11-02
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Appbase can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.