Olaia: Ship your full stack effortlessly. On European infrastructure.

Showing 25 of 78 from the live probe.

• Connect Olaia account

  Start browser-based Olaia MCP pairing for a user who already has an Olaia account. Return a dashboard approval URL and pairing code. Always show connect_url to the user as a clickable link and ask them to confirm the code before approving. If the user does not have an account yet, use olaia_sign_up instead.

• Help user sign up for Olaia

  Start browser-based Olaia signup and MCP pairing. This tool does not create the account for the user. It returns register_url and a pairing code so the user can sign up, verify their email, and approve this agent connection in Olaia. Always show register_url to the user as a clickable link, ask them to confirm the pairing code, and after they approve call olaia_connect_status.

• Check Olaia connection

  Poll the browser-based Olaia MCP pairing flow. If approved, the MCP server stores the agent key internally and future Olaia tools will work. The key is never returned to the agent.

• Describe Olaia MCP capabilities

  Discover Olaia MCP capability groups and exact tools. Use this before less-common work such as database writes, Storage, Auth, or Compute so the agent chooses the safest available tool.

• Current Olaia agent context

  Return the Olaia account, agent key scope, limits, and platform config for this MCP session.

• Connect GitHub to Olaia

  Return a dashboard URL for the user to connect GitHub to Olaia. Always show connect_url to the user as a clickable link. Do not ask for GitHub credentials. After the user completes the browser flow, call olaia_github_status every 5-15 seconds with light backoff until it reports connected or about 10 minutes pass.

• Check GitHub connection

  Check whether GitHub is connected to Olaia and list accessible repositories. Pass repo as owner/name or a GitHub URL when you need to confirm a specific repository is accessible. If repo is not accessible, show connect_url and ask the user to update GitHub repository access in Olaia.

• Link Olaia git remote

  Create an Olaia deploy token and return clone/push commands for a project's Olaia git remote. Use this when code is stored in Olaia, when the project was created from ZIP, or when the user does not want GitHub. The token can clone/read source and push code for previews for this project only; it cannot call the Olaia API, read env values, secrets, database rows, storage objects, or promote production. Store it with the git credential helper, not in app code, env vars, logs, or chat. Every push bu

• Check Olaia git remote status

  Inspect source access for a project, including clone URL, Olaia git remote URL, deploy-token prefixes, branch preview status, latest commit identity, image tag, and preview URL. Use after git push and poll until the latest preview is live. Once live, the response includes promotion.approval_url for the pushed preview. Always show approval_url to the user as a clickable link so they can review the preview and promote it to production.

• Contact Olaia support

  Send a short plain-text support request to Olaia at info@olaia.eu. Use this when the user explicitly wants Olaia support or when the platform is blocked by an Olaia-side issue. Do not include secrets, credentials, access tokens, raw private data, or attachments.

• List projects

  List projects visible to this agent key.

• Get project

  Return full project detail for a project in this agent key's scope, including clone_url for reading the project's source code. GitHub projects return the GitHub repo URL; Olaia-hosted and ZIP projects return the Olaia git clone URL.

• Create project

  Create an empty or GitHub-backed project. No production deployment is created. For GitHub-backed projects, call olaia_github_status first if you need to confirm the repository or installation_id.

• List project domains

  List custom domains for a project, including domain connection status, HTTPS status, setup records, and the next recommended action.

• Add custom domain

  Add a custom domain to a project and return simple setup instructions for the user's domain provider. Always show domain.setup.user_guidance and domain.setup.records to the user. The user must update their domain provider, then you should call olaia_project_domains_check.

• Check custom domain

  Check whether the user's domain provider is pointing the domain to Olaia. If connected, Olaia starts HTTPS automatically. If not connected, repeat the returned setup instructions in plain language.

• Retry custom domain HTTPS

  Retry HTTPS certificate setup after the domain is connected but HTTPS failed. Use only when domain.status is domain_connected_https_failed. If retry fails again, recommend contacting Olaia support.

• Remove custom domain

  Remove a custom domain from a project. Use only when the user explicitly asks to remove it.

• List project environment names

  List environment variable names and filled/empty status for a project. Values are never returned.

• Propose environment variables

  Create empty env placeholders and return a dashboard link for the human to paste values. Agents cannot submit or read values.

• List databases

  List databases visible to this agent key. Returns metadata only.

• Create managed database

  Create an Olaia-managed Postgres database. Use this whenever an app needs persistent or shared storage instead of local files. Optionally connect it to a project; the database URL is injected server-side and never returned. Use the injected connection string as-is: Olaia includes sslmode=disable because project-to-database traffic runs over a private internal network.

• Attach database to project

  Connect an existing Olaia-managed database to a project. The database URL is injected server-side and never returned. Use the injected connection string as-is: Olaia includes sslmode=disable because project-to-database traffic runs over a private internal network.

• Inspect database schema

  Inspect database schemas, tables, columns, indexes, foreign keys, and estimated row counts. Does not return row data.

• Query database with masking

  Run a SELECT/WITH query against an Olaia Postgres database. Results are masked by the Olaia gateway: sealed values are never returned, sensitive values are redacted, and raw row data requires a separate human data-reveal approval.