MATLOOK Connect & extend
Connect sources
Give MATLOOK Agent access to selected folders, APIs or MCP services with a clear purpose.
Choose an MCP or API catalog template (desktop RC45 onward)#
Open Settings → Skill Marketplace, browse the MATLOOK catalog and filter by MCP or API. Review the address, authentication method and instructions before adding it to the current workspace. Then open the source details to supply your own credentials and test the connection. Existing same-name sources are preserved. Administrators publish templates without shared secrets. Never paste credentials into template prose, URLs or command arguments. HTTP/SSE MCP requires an accessible service. A local stdio MCP starts the previewed program when used, and that program must already be installed; adding a template does not install third-party MCP software. If an entry changes or is withdrawn after preview, refresh before adding. Withdrawal does not delete installed sources. Existing manual API, MCP and local-source setup remains available. New catalog controls currently use Chinese labels.
Choose a source type#
| Type | Common purpose | Preparation |
|---|---|---|
| Local folder | Catalogs, quotations and project archives | A directory accessible on the execution target |
| API | Material databases, business systems or notifications | Endpoint, authentication and interface documentation |
| MCP | Tools provided by local or remote services | Launch configuration or address, authentication and tool list |
Add and use a source#
- Open Sources in the feature rail and add the appropriate type.
- Give it an accurate name and purpose, such as “Demo hotel references — read for research”.
- Configure and check the connection. Start API and MCP testing with a low-impact query.
- Select the needed source in your conversation and specify what to retrieve.
- Verify the tool result came from that source rather than model memory.
Local-folder boundaries#
Adding a folder does not automatically upload the entire directory. Content actually supplied to an online model uses that connection. Remote access requires a valid path on the target computer.
Troubleshooting#
Check the address, launch command, network, credentials and tool permissions. The web app may not offer a native folder picker. Keep keys, token-bearing URLs and private catalogs out of public feedback.
Expected result#
Retrieve a known item and identify its source. A successful connection does not grant access to every workspace or endpoint.