Hosted MCP server/Other

Lim ://ServerByLim MCP server

Hosted at lim.base44.app·Streamable HTTP

Lim exposes an MCP endpoint at https://lim.base44.app/api/mcp. The live server identifies itself as Base44 App and lists a large set of query_<entity> tools for Lim records, including chats, accounts, ads, AdSense sites, AI downloads and shares, business listings, calendar events, classrooms, forms, games, mail, media, notes, sites, tasks, and more. The provider homepage does not document the MCP server, its auth, or its tool list, so treat the tools/list response as the current reference and review permissions in the client.

lim.base44.app Streamable HTTP Not verified Server not checked yet Reviewed 2026-11-16
About

Where it fits

Lim users who want to query their app's records from an MCP client and are comfortable reviewing the exposed tools.

  • Query Lim chat or account records.
  • Browse business listings or tasks.
  • Review the tool list before granting access.

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.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds Lim ://ServerByLim as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http lim-serverbylim https://lim.base44.app/api/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://lim.base44.app/api/mcp
Host
lim.base44.app · /api/mcp
Transport
Streamable HTTP
Authentication
Not verified
Server name
lim-serverbylim
Listing type
Community or directory listing

The installer uses the server name lim-serverbylim. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that lim-serverbylim appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Query Lim chat or account records. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Confirm the provider's credential model before relying on scopes or key permissions. Remove the server and revoke any token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

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.
Safety

Before you connect

Remote means provider access
  • 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.
Review path

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.