SourceSync.ai MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validateApiKeyA | Validates the API key by attempting to list namespaces. Returns the list of namespaces if successful. |
| createNamespaceC | Creates a new namespace with the provided configuration. Requires a name, file storage configuration, vector storage configuration, and embedding model configuration. |
| listNamespacesB | Lists all namespaces available for the current API key and optional tenant ID. |
| getNamespaceC | Retrieves a specific namespace by its ID. |
| updateNamespaceC | Updates an existing namespace with the provided configuration parameters. |
| deleteNamespaceC | Permanently deletes a namespace by its ID. |
| ingestTextC | Ingests raw text content into the namespace. Supports optional metadata and chunk configuration. |
| ingestFileC | Ingests a file into the namespace. Supports various file formats with automatic parsing. |
| ingestUrlsC | Ingests content from a list of URLs. Supports scraping options and metadata. |
| ingestSitemapC | Ingests content from a website using its sitemap.xml. Supports path filtering and link limits. |
| ingestWebsiteC | Crawls and ingests content from a website recursively. Supports depth control and path filtering. |
| ingestConnectorC | Ingests all documents in the connector that are in backlog or failed status. No need to provide the document ids or file ids for the ingestion. Ids are already in the backlog when picked thorough the picker. If not, the user has to go through the authorization flow again, where they will be asked to pick the documents again. |
| getIngestJobRunStatusC | Checks the status of a previously submitted ingestion job. |
| fetchDocumentsC | Fetches documents from the namespace based on filter criteria. Supports pagination and including specific document properties. |
| updateDocumentsC | Updates metadata for documents that match the specified filter criteria. |
| deleteDocumentsC | Permanently deletes documents that match the specified filter criteria. |
| resyncDocumentsB | Reprocesses documents that match the specified filter criteria. Useful for updating after schema changes. |
| semanticSearchC | Performs semantic search across the namespace to find relevant content based on meaning rather than exact keyword matches. |
| hybridSearchC | Performs a combined keyword and semantic search, balancing between exact matches and semantic similarity. Requires hybridConfig with weights for both search types. |
| createConnectionB | Creates a new connection to a specific source. The connector parameter should be a valid SourceSync connector enum value. The clientRedirectUrl parameter is optional and can be used to specify a custom redirect URL for the connection. This will give you a authorization url which you can redirect the user to. The user will then be asked to pick the documents they want to ingest. |
| listConnectionsB | Lists all connections for the current namespace, optionally filtered by connector type. |
| getConnectionC | Retrieves details for a specific connection by its ID. |
| updateConnectionC | Updates a connection to a specific source. The connector parameter should be a valid SourceSync connector enum value. The clientRedirectUrl parameter is optional and can be used to specify a custom redirect URL for the connection. This will give you a authorization url which you can redirect the user to. The user will then be asked to pick the documents they want to ingest. This is useful if you want to update the connection to a different source or if you want to update the clientRedirectUrl or if you want to pick a different or new set of documents. |
| revokeConnectionC | Revokes access for a specific connection, removing the integration with the external service. |
| fetchUrlContentC | Fetches the content of a URL. Particularly useful for fetching parsed text file URLs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
Most tools have distinct purposes, but some overlap exists. For example, ingestFile, ingestText, ingestUrls, ingestWebsite, and ingestSitemap all handle ingestion from different sources, which could cause confusion. However, their descriptions clarify the specific input types, helping to differentiate them. The search tools (semanticSearch, hybridSearch) are clearly distinct, and CRUD operations for connections, namespaces, and documents are well-separated.
Tool names follow a highly consistent verb_noun pattern throughout, such as createConnection, deleteNamespace, fetchDocuments, and updateDocuments. All tools use camelCase uniformly, with no mixing of naming conventions. This predictability makes it easy for agents to understand and use the toolset.
With 25 tools, the count is borderline high for a document ingestion and search server. While the tools cover a broad range of operations (connections, namespaces, ingestion, search, updates), it may feel heavy and potentially overwhelming. A more focused set could improve usability, but the count is not extreme.
The toolset provides comprehensive coverage for the domain of document ingestion and management. It includes full CRUD operations for connections, namespaces, and documents, multiple ingestion methods (files, text, URLs, websites, sitemaps), search capabilities (semantic and hybrid), and utility functions like validation and status checks. There are no obvious gaps that would hinder agent workflows.