Hosted MCP server/Marketing Official

Official Almirall MCP server

Hosted at mcp.almirall.com·Streamable HTTP

Almirall MCP Official is listed as a search and retrieval server over Almirall's indexed website content, returning pages, sources, products and embedded assets. The provider publishes no MCP reference or setup documentation: the only linked page is the Almirall corporate homepage, which does not mention MCP. The endpoint is unverified and authentication is unknown.

mcp.almirall.com Streamable HTTP Not verified Source checked Oct 31, 2026 Server not checked yet Reviewed 2026-11-16
About

Where it fits

People researching Almirall products who want an assistant to search the company’s indexed site content.

  • Find pages that discuss a specific Almirall product.
  • Retrieve source material behind a site claim.
  • Locate embedded assets tied to a product page.

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 Almirall as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http almirall https://mcp.almirall.com/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://mcp.almirall.com/mcp
Host
mcp.almirall.com · /mcp
Transport
Streamable HTTP
Authentication
Not verified
Server name
almirall
Listing type
Official provider listing

The installer uses the server name almirall. 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 almirall appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Find pages that discuss a specific Almirall product. 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. The provider page was available when we checked.

Provider page available on Oct 31, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

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.