Summary
Search digital catalogs (Kataloge), product datasheets, technical drawings, safety data sheets, and media assets via Oxomi — the dominant catalog/media portal for the German Baustoff (building materials) trade. Use for product lookup, document download, and cross-selling research across thousands of supplier catalogs.
Guided setup
Connect Oxomi Product & Media Portal to Microsoft Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect Oxomi Product & Media Portal in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for Oxomi Product & Media Portal
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Oxomi Catalog & Media Portal, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
Oxomi Catalog & Media Portal + Microsoft Copilot
Search digital catalogs (Kataloge), product datasheets, technical drawings, safety data sheets, and media assets via Oxomi — the dominant catalog/media portal for the German Baustoff (building materials) trade. Use for product lookup, document download, and cross-selling research across thousands of supplier catalogs.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
OXOMI_PORTAL_ID, OXOMI_USER, OXOMI_ACCESS_TOKEN, OXOMI_API_TOKEN
Step 1 — Get credentials
Credentials
Enter these when importing the connector; they are injected as query parameters on every call:
OXOMI_PORTAL_ID— your numeric portal id (e.g. 3001049)OXOMI_USER— your Oxomi portal user (set a non-empty value; used for profile-scoped access)OXOMI_ACCESS_TOKEN— the portal API access token (Portal-Einstellungen → API)OXOMI_API_TOKEN— the API-Token ID, required ONLY by the product-sync tools (oxomi_sync_products_changed,oxomi_get_product_spx,oxomi_update_sync_date). Leave unset if you don't use sync.
…(continued in the in-app connector instructions)
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Microsoft Copilot
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
- Try it in the agent's Test pane: ask for something that needs the
Oxomi Catalog & Media Portaltools. - Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.
Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
oxomi_search_products | Search products across all suppliers in the portal by SKU, EAN, or description |
oxomi_get_product_data | Fetch rich product information for a product (by itemNumber + supplierNumber): images, attachments/documents, prices, catalog pages, cover… |
oxomi_resolve_gtin | Resolve a GTIN-13 or GTIN-14 barcode to its product, returning the supplierNumber and supplierItemNumber |
oxomi_product_availability | Obtain manufacturer stock/availability for a product (stock status, indicator, availability dates, manufacturing time) |
oxomi_get_brand_info | Get information about a brand by id, name or supplier number: official name, supplier number(s), logo image URL, manufacturer and… |
oxomi_list_documents | List documents (catalogs, price lists, brochures, promotions, etc.) in the portal with filtering and pagination |
oxomi_render_datasheet | Render the technical datasheet of a product and return the generated HTML in a JSON response |
oxomi_sync_products_changed | Incrementally sync products changed since a given date from the product information graph (for ETL/bulk export) |
oxomi_get_product_spx | Fetch a single product in full SPX format by itemNumber or GTIN, with selectable data blocks |
oxomi_update_sync_date | Update the stored sync date for the portal API token (call after a successful incremental sync so the next run starts from the right point) |
FAQ
Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.
What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.
The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.
Next steps
- Connector landing page
- Connect to Claude
- Connect to ChatGPT
- Connect to Cursor
- Connect to Gemini
- Connect to Meta Muse
Was this guide helpful?