Skip to main content
Glama
abushadab

Self-Hosted Supabase MCP Server

by abushadab

get_project_url

Retrieve the configured Supabase project URL from the Self-Hosted MCP Server, enabling direct access to Supabase features and database interactions within MCP-compatible environments.

Instructions

Returns the configured Supabase project URL for this server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that executes the tool logic. It retrieves the Supabase project URL from the provided client context and returns it in the expected output format.
    execute: async (input: GetProjectUrlInput, context: ToolContext) => {
        const client = context.selfhostedClient;
        const url = client.getSupabaseUrl(); // Use getter from client
        return { project_url: url };
    },
  • Zod schemas for input (empty), output (project_url as URL string), and static MCP JSON input schema (empty object).
    const GetProjectUrlInputSchema = z.object({});
    type GetProjectUrlInput = z.infer<typeof GetProjectUrlInputSchema>;
    
    // Output schema
    const GetProjectUrlOutputSchema = z.object({
        project_url: z.string().url(),
    });
    
    // Static JSON Schema for MCP capabilities
    const mcpInputSchema = {
        type: 'object',
        properties: {},
        required: [],
    };
  • src/index.ts:18-18 (registration)
    Import statement for the getProjectUrlTool.
    import { getProjectUrlTool } from './tools/get_project_url.js';
  • src/index.ts:107-107 (registration)
    Registration of the getProjectUrlTool in the availableTools object, making it available for the MCP server.
    [getProjectUrlTool.name]: getProjectUrlTool as AppTool,
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It indicates a read-only operation ('Returns') and specifies the data source ('configured... for this server'), but does not disclose behavioral traits like error conditions, authentication needs, or rate limits. It adequately describes the core behavior without contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded with the key action and resource, making it easy to parse and understand immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is complete enough for basic understanding. However, it lacks details on the return format (e.g., string type, potential null values) or error handling, which could be helpful despite the low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the schema description coverage is 100%, so no parameter documentation is needed. The description does not add parameter details beyond the schema, but this is appropriate given the lack of parameters, warranting a baseline score above minimum.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Returns') and the exact resource ('configured Supabase project URL for this server'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'get_anon_key' or 'get_service_key' by focusing on the project URL rather than other configuration elements.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when the Supabase project URL is needed, but it does not explicitly state when to use this tool versus alternatives (e.g., other 'get_' tools for different configuration items) or any prerequisites. The context is clear but lacks explicit guidance on selection among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/abushadab/selfhosted-supabase-mcp-basic-auth'

If you have feedback or need assistance with the MCP directory API, please join our Discord server