Where it fits
Developers evaluating a hosted Postgres backend for AI-built apps, pending provider MCP documentation.
- Preview a schema change before applying it.
- Review backups and logs for a hosted database.
- Check row-level security before a schema change.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with Scribase
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Improves application speed across the frontend, backend, database, and query layers. Reach for it when a performance target exists, a regression is suspected, Core Web Vitals or load times need work, N+1 queries need fixing, or profiling has exposed a bottleneck.
Creates and edits Obsidian Bases, the .base files that hold views, filters, formulas, and summaries. It applies to work with .base files, database-like views over notes, and references to Bases, table views, card views, filters, or formulas in Obsidian.
Lark Base (multidimensional tables): create tables, fields, records, views, statistics, formulas and lookups, forms, dashboards, app modes (BaseApp/AppMode pages and components), Workspace directories, workflows, role permissions, and the template center (Base template categories, lists, and search). Use for Base, bitable, BaseApp or AppMode work, or /base/ and /app/ links. BaseApp does not go through lark-apps; file import and export go to lark-drive, and authentication or authorization goes to lark-shared.
No skills found
Try a different search term or clear the filters.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
- The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
Scribase documentationhttps://scribase.com/migrate