Claude Metal connectorWhat Claude can do in your Metal account.

Lists companies using structured filters only, such as sector, tag, team or location, with no free-text query involved.

Finds companies by name using a mix of semantic and keyword matching, so a partial or approximate name still surfaces the right record. The matching runs on company names only, not on the rest of the profile.

Returns the company tags your firm uses, with their exact IDs, so Claude can filter companies on the right tag instead of guessing its spelling.

Retrieves the full profile of one company from its ID, the record Claude works from once the search has found the right match. It takes the company ID that a search or a filtered list returns.

Returns the extracted text of a document by line number, which lets Claude quote a passage precisely and point to where it sits.

Looks through the content of documents, or lists them by type and date, across what your account can see in Metal.

Finds contacts by name, title, company or email, so Claude can find the right person among your firm's contacts. It searches your contacts, which are distinct from the Metal users that search_users finds.

Looks up colleagues who use Metal by name or email. A query is required, so this is for finding someone specific rather than browsing everyone.

Retrieves one Metal user from an ID, typically after a search or when another record points to that person as an owner. It returns a Metal user, a colleague with an account, not an outside contact.

Returns the teams of your organization with names and IDs, which Claude then reuses to filter deals and companies by team. The list covers every team in your organization, not only yours.

Retrieves a single team from its ID, the step after the team list when Claude needs that team's own record rather than a name. It takes the team ID that list_teams returns.

Lists the workflows Claude can see, with their IDs, page by page. Metal notes that it includes your organization's configured workflows plus visible Metal-provided global ones.

Gives an overview of one workflow's definition, optionally for a given version, including what it expects as input, so nothing is launched with a missing field.

Finds workflow runs filtered by the record they concern, their status or dates, with pagination for long histories. A run can be looked up from the record it concerns, by that record's type and ID.

Returns a run's status and outputs, with shortcuts to view steps, errors, artifacts or citations, so Claude can report in plain terms what the workflow produced.

Searches or filters deals, with the text query optional when filters are enough, so Claude can answer pipeline questions directly.

Pulls up one deal's full record from its ID, once a search has pointed to the right deal. Metal describes it as the full deal record, not an excerpt.

Retrieves the complete profile of one contact from an ID, after a search has found the right person. It returns a contact record, as opposed to a Metal user account.

Returns the lists your organization keeps in Metal so Claude knows which ones exist before opening any. Metal calls them resource lists; their rows come through a separate tool.

Retrieves a list's metadata and column schema. It does not include the rows themselves; those come from the entries tool, which Claude calls next.

Reads a list's rows page by page through a cursor, so Claude can work through long lists in successive pages. It is the tool that holds the row data get_list leaves out.

Returns the meetings, calls and interactions recorded for a company, so Claude can lay out the history of contact with it. It works at the level of one company.

Opens one activity in full, with its participants, linked deals and attached documents, so Claude can recount one interaction in full detail. It takes the ID of a single activity, such as one listed for a company.