Ist es möglich, externe MCP-Clients (z. B. n8n, Langdock) mit mcp_WordServer zu verbinden?

Please note that this is the de-de forum. We kindly recommend posting your question in German so that more community members can assist you. Alternatively, you may consider posting in the German forum if you prefer to use your native language. We sincerely appreciate your understanding.

Hi Jan Küchli (DEV)

Thank you for reaching out to Microsoft Q&A forum

First of all, I’d like to start by acknowledging that some of the resources you mentioned, such as n8n or Langdock, are outside the scope of Microsoft support. In my role as a forum moderator, I’m limited to referencing official Microsoft documentation, which means I may not be able to provide a definitive solution to this particular issue.

However, if your goal is to connect to mcp_WordServer to external MCP Clients I encourage you to follow the official Microsoft guidelines provided below:

Confirm the MCP server type and endpoint, then verify access & network reachability

• Identify whether you’re connecting to a managed/external Microsoft MCP server (e.g., Databricks MCP) or a custom/self‑hosted MCP server and obtain the server URL(s).
• Validate that your account has rights to the target resources and that any IP allowlisting or firewall rules permit the external client (n8n/Langdock) to reach the MCP endpoint over HTTP/SSE.

Choose the right authentication model, prefer OAuth for production

• OAuth 2.0 (with automatic refresh and scoped permissions) is the recommended, high‑security option for long‑lived, team integrations.

Configure the client (n8n or Langdock) to the MCP server with the selected auth flow

• In the client, add a new MCP connection: supply the MCP server URL, select OAuth or PAT/API key (depending on server capabilities), and complete the authorization flow.
• After connecting, discover tools/resources published by the MCP server and test to confirm the client can list and invoke MCP tools.

Finally, kindly enforce token validation (audience binding, JWKS signature checks), correct WWW‑Authenticate handling (401/403), and avoid token passthrough/“confused deputy” risks. For custom servers, expose the appropriate .well-known authorization metadata and implement authorization middleware.

You can read here for more information:

Connect non-Databricks clients to Databricks MCP servers

Extend your agent with Model Context Protocol

Hope my answer will help you, for any further concern, kindly let me know in the comment section.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".     

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Hallo,

vielen Dank für deine Anfrage.

Stelle Fragen im deutschsprachigen Forum immer in deutscher Sprache ein.

Kontaktiere die jeweiligen Hersteller für Unterstützung.

Bei Fragen zu Microsoft 365/Office stehen wir zur Verfügung.