Connect your first App and call its tools from an MCP-compatible client.
This guide walks through the full flow with the file connector: create a connection, review the automatically generated tools, set up Connector in a client, and make your first call. It takes about 10 minutes.
Click the File connector card to open its details page, which has two sections:
A tool can only find content if the connector holds data. Data in the file connector is organized into categories.
Connector exposes its service through a single MCP endpoint, which covers every connected App in the current workspace.
Ask a question in natural language in your client, for example:
The client calls the search files tool and returns the list of matching files along with their download links.
Prerequisites
- An Alibaba Cloud account with Alibaba Cloud Model Studio activated.
- An Alibaba Cloud Model Studio workspace and its workspace ID, in the form
llm-xxxxxxxxxxxx. - A DashScope API Key, created on the API-KEY page of the Alibaba Cloud Model Studio console.
- An MCP-compatible client, such as Qoder.
For RAM users, the Alibaba Cloud account must grant authorization before Connector can be used.
Step 1: Create a connection
- Open the App catalog: Go to the Connector console and click Apps in the left-side navigation. The page lists every App you can connect.
-
Choose the file connector: Find the File connector card and click Connect on the card.
The file connector hosts unstructured documents such as PDF, Word, and Markdown files. It requires no credentials from an external system, which makes it the easiest way to complete the flow for the first time.
For Apps such as Yuque, Salesforce, and MaxCompute, the connection dialog contains only an auth config dropdown, so you have to create an auth config before you can connect. For the workflow, see Authentication overview.
-
Fill in the connection details. In the dialog box that appears, provide the following:
Field Required Description Connector name Yes Distinguishes multiple connections under the same App, up to 64 characters. For example, Product docs libraryConnector description No Explains what this connection stores and when to use it. Agents rely on the description to decide whether to call it, so be specific Storage location Yes Only one option, Use platform storage, which keeps the data within the free storage quota provided by the platform - Confirm the creation: Click Confirm. Back on the Apps list, the file connector card shows the number of connections you have created.
Step 2: Review the automatically generated tools
Click the File connector card to open its details page, which has two sections:
- Connected users: lists every connector instance under this App, with its name, status, and creation time. Click the edit icon next to a name to rename it.
- Available tools: the tools Connector generated automatically. Expand any tool to see its input and output parameters.
| Tool | Function | Input parameters |
|---|---|---|
| Search files | Queries the file list by keywords in file titles and returns file download links | keyWord (string, required): keyword in the file titlemaxCount (integer, optional): number of results to return, default 5, max 10 |
| Get file | Retrieves a file by its ID and returns the file download link | fileId (string, required): the file ID |
Tools are generated automatically once a connection is established. Their number and parameters are determined by the App type, so there is no need — and no way — to configure them manually. Different Apps generate different tools. For details, see the documentation for each App.
Step 3: Import a few files
A tool can only find content if the connector holds data. Data in the file connector is organized into categories.
- Create a category: Open the file management page of the connector and create a category in the category pane on the left, for example
Product manuals. - Upload files: Click Import data, choose local upload as the import method, and select a few PDF or Word files.
- Wait for parsing to finish: The platform converts the files into a searchable format. Parsing can take a while when there are many files or during peak hours.
Step 4: Set up your client
Connector exposes its service through a single MCP endpoint, which covers every connected App in the current workspace.
- Find the MCP configuration entry: Locate the MCP or connector configuration entry in the client you use.
-
Add the MCP server. Add the following configuration to the client's MCP configuration file:
-
Replace the two variables:
- Replace
${workspaceId}with your Alibaba Cloud Model Studio workspace ID. - Replace
${DASHSCOPE_API_KEY}with your DashScope API Key.
- Replace
-
Verify the connection: Save the configuration, then restart or refresh the client. In the MCP server list, confirm that
bailian-connector-mcpshows as connected and that expanding it reveals the tools provided by Connector.
Step 5: Make your first call
Ask a question in natural language in your client, for example:
Troubleshooting connection failures
| Symptom | Possible cause |
|---|---|
| Returns 401 | The authentication header is missing, or the API Key is invalid or expired |
| Returns 404 | The MCP endpoint is wrong. Check that the path is /api/v2/connector/mcp |
| Shows as disconnected in the server list | The workspace ID is incorrect, or the network cannot reach cn-beijing.maas.aliyuncs.com |
| Connected but the tool list is empty | The current workspace has no connected Apps yet |
Next steps
- Core concepts: Understand the hierarchy of Apps, connector instances, and tools.
- Connect more Apps: Connect real business systems such as DingTalk, Yuque, and databases.
- Authentication: Create an auth config before you connect Yuque or Salesforce.
- Manage files and categories: Organize files with categories and import them from your machine or in bulk from OSS.