WingloDocs

MCP servers and tools

Learn what MCP servers and tools are, how Winglo discovers capabilities, and how to connect directory or custom servers safely.

Model Context Protocol (MCP) lets a service describe tools that an AI system can call. In Winglo, an MCP server is a connection; each advertised capability appears as a separate tool that you can control.

How MCP fits into Connectors#

Open Connectors and choose the MCP servers filter to browse available servers. The connector summary shows how many servers are connected, how many tools have been discovered, and how many require approval.

Opening a server before connection shows its description and the capabilities listed for it. After connection, Winglo displays the tools the server advertises and the access settings available for your departments.

Connect a directory server#

  1. Open the server card.
  2. Read its description and advertised capabilities.
  3. Choose Connect.
  4. Complete the provider authorization.
  5. Return to Winglo and check that the server says Connected.
  6. Review every discovered tool before enabling it.

If setup remains at Finishing setup, reopen the connection and complete the authorization. If the server says Needs attention, read the displayed error before reconnecting.

Add your own server#

When Your own servers is available, choose Add server, enter the HTTPS server URL, and optionally add a recognizable name. Use only an address supplied by a service you trust and that your organization has approved.

A custom server is not automatically reviewed by Winglo. Treat its descriptions, inputs, and read/write labels as claims made by that server. Grant its tools one at a time after checking what each tool receives and can change.

Do not place tokens, passwords, or secrets in the server URL. Use the authorization flow offered after the URL is added.

Understand discovered tools#

A tool can include a name, description, declared inputs, and publisher-provided labels such as READ or WRITE. A missing label does not prove that a tool is safe or read-only. Publisher classifications are not a substitute for your own review.

Before enabling a tool, ask:

  • What information will it receive?
  • Can it create, update, send, publish, or delete anything?
  • Which department needs it?
  • Should a person approve every use?

Some tools copy inputs into network headers. Winglo displays a warning when that is declared. Do not use such a tool for information you would not place in a URL.

Disconnect or remove a server#

Disconnect when you want to stop new tool calls but may need the setup again. Use permanent removal only after reading the confirmation. Removal can also erase the connection's grants, discovered tools, cached resources, and call history.

Neither action reverses changes the server already made in another service. Review provider-side access separately.

Next, read Manage MCP tool access and Create and manage triggers.