# CloudCard ID Photos MCP > CloudCard ID Photos manages your entire identity card lifecycle, from new person registration to photo approval. Use this MCP to programmatically list submitted photos, check if they meet organizational standards, and approve or deny submissions with specific reason codes—all through a single chat session. ## Overview - **Category:** productivity - **Price:** Free - **Tags:** id-management, photo-approval, cardholder-data, onboarding, identity-verification, workflow-automation ## Description Managing employee and student identities involves more than just printing cards; it's a complex workflow that requires continuous data checks and approvals. This MCP connects your agent directly to the CloudCard platform, letting you handle everything from initial registration to final photo sign-off without switching apps. You can find out exactly what photo dimensions are required using one command, then check existing people’s records with details like their submission history. Need to add a new person? Just register them and move on. If the photos are ready for review, you can list all pending submissions. Your agent handles the approval process—you tell it to deny a photo because the background is wrong, or approve it if it passes muster. Since Vinkius hosts this MCP in the catalog, your AI client treats it like any other essential service: just another tool at your fingertips. ## Tools ### approve_id_photo Approves a specific photo submission record so the ID can move forward in production. ### check_api_health Verifies that the connection to CloudCard is active and working properly right now. ### register_new_cardholder Adds a new person record using only their email and full name. ### deny_id_photo Rejects a photo submission, requiring you to provide a reason code or message for the person. ### get_authenticated_profile Retrieves the API user's own information to confirm who is running the process. ### get_organization_settings Retrieves general metadata about the entire organization's configuration within CloudCard. ### get_cardholder_details Fetches all stored details for a specific person, like their name and submission history. ### list_card_offices Lists all physical locations where ID cards are distributed or managed. ### list_cardholders Retrieves a list of every person currently stored in the system. ### list_submitted_photos Lists all photos that have been submitted to CloudCard, with options to filter by status (pending, approved, etc.). ### list_photo_requirements Gets the specific rules for photo submissions, including size and background format. ### list_configured_webhooks Shows all active event webhooks that are configured to notify other systems. ## Prompt Examples **Prompt:** ``` List all pending photo submissions in CloudCard. ``` **Response:** ``` I've found 12 pending photo submissions. Notable ones include John Doe (ID: 123) and Alice Smith. Would you like to review their photos? ``` **Prompt:** ``` Deny photo ID '789' because the background is not plain white. ``` **Response:** ``` Done! I've denied photo '789' with the reason: 'Background is not plain white'. The cardholder will be notified. ``` **Prompt:** ``` Show me the details for cardholder 'john@example.com'. ``` **Response:** ``` I've retrieved John Doe's profile. He has one approved photo and his physical ID card was picked up at the Main Office on April 10th. ``` ## Capabilities ### Review submitted photos List all photo submissions and check which ones are pending approval. ### Approve or deny photos Change a submission's status by approving it or denying it, providing a required reason code if the denial is necessary. ### Register new people Add a brand new cardholder profile to the system using basic identifying information like name and email. ### Look up person details Retrieve detailed profiles, including submission history, for any specific individual in the database. ### Check organizational rules Get current photo standards and dimensions required by your organization. ### Monitor system health Verify that the CloudCard API connection is currently working correctly. ## Use Cases ### Handling a large class intake The Registrar needs to review 50 student photos. Instead of manually checking each one against dimensional rules and then logging in to approve them, they ask their agent to list all pending submissions using `list_submitted_photos`. The agent finds the batch, checks if required standards are met via `list_photo_requirements`, and approves the whole group. ### Onboarding a new department HR needs to start tracking staff for a new campus location. They use `list_card_offices` to confirm the location is recognized, then they use `get_organization_settings` to pull necessary metadata before using `register_new_cardholder` for the first batch of employees. ### Investigating a bad photo submission A security manager notices an ID card was rejected. They use `get_cardholder_details` to pull up the person's file, see their full submission history, and then check for any related alerts by reviewing configured webhooks via `list_configured_webhooks`. ### Quickly verifying a profile A staff member needs to know if a vendor is already registered in the system. They ask their agent to list all cardholders using `list_cardholders`, and then narrow down the record by calling `get_cardholder_details` for that specific person. ## Benefits - Stop guessing what photos are allowed. Use the `list_photo_requirements` tool to get exact rules for dimensions and backgrounds before approving anything. - Handling submissions is fast. Instead of logging into a web portal, you simply ask your agent to list pending submissions using `list_submitted_photos`, getting an immediate overview. - New people are easy to onboard. Use the `register_new_cardholder` tool to add basic records instantly, then get their full file history later with `get_cardholder_details`. - Approval is simple and compliant. You can approve or deny photos directly by asking your agent; you'll need to use `deny_id_photo` if the photo fails standards. - You maintain oversight of everything. Check system health using `check_api_health` before running any major batch job, ensuring data integrity throughout the process. ## How It Works The bottom line is, instead of logging into a web portal, you talk to your agent and it handles the backend workflow. 1. Subscribe to this MCP and enter your required CloudCard API Token (X-Auth-Token). 2. Use natural language commands in any compatible client, telling the agent exactly which action you need—for example, 'List all pending ID photos for department X.' 3. The MCP executes the request against CloudCard and returns structured data or confirmation messages directly to your chat interface. ## Frequently Asked Questions **How do I check if photo submissions are ready for approval using list_submitted_photos?** You ask your agent to run `list_submitted_photos`, specifying filters like 'status: pending'. This gives you a clean, current view of every submission that needs human eyes. **What must I know before using approve_id_photo?** You must first confirm the photo meets organizational standards. Running `list_photo_requirements` ensures you have the correct dimensions and background type before attempting to approve anything. **Does list_cardholders show every single person I've ever worked with?** It lists everyone currently stored in the CloudCard database. If you need detailed history for one specific person, use `get_cardholder_details` instead. **What is the best way to add a new employee record? Use register_new_cardholder?** Yes, that's right. The `register_new_cardholder` tool handles adding basic records using just their email and name. It gets them into the system fast. **Before I approve or deny a photo, how do I verify my agent's own access level using get_authenticated_profile?** The tool returns your current API user information. This confirms the credentials your AI client is operating under. Always check this first to ensure you have the necessary permissions for sensitive actions. **My team needs specific photo specs; how can I verify organizational standards using list_photo_requirements?** It gives you all the mandated details, including required size, format, and background specifications. This is essential knowledge before submitting or approving any ID photos. **If my workflow suddenly fails, what command should I use to check for system connectivity issues? Use check_api_health.** You run `check_api_health` immediately. It verifies if the CloudCard API connection is live and responding correctly. This confirms that the problem isn't just a network outage. **We need to track changes automatically; what does list_configured_webhooks show me about our active event monitoring?** This tool lists all webhooks currently configured for your account. It confirms which events are actively broadcasting data to external systems, ensuring no critical updates are missed. **How do I get a CloudCard API Token?** Log in to your [**CloudCard Admin**](https://app.cloudcard.us/) portal, go to your Profile or Settings, and generate an API Token (X-Auth-Token). **Can the agent auto-approve photos?** Yes, using the `approve_id_photo` tool, the agent can approve any pending photo submission once verified through conversation. **Is student ID management supported?** Absolutely. CloudCard is widely used in higher education, and this server supports registering students and managing their photo submissions.