Behance 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_behance_projectsA | Search for projects on Behance by keyword. Returns project ID, title, URL, creator info, thumbnails, stats (views, appreciations, comments), and creative fields. |
| get_behance_project_detailsA | Get detailed information about a specific Behance project including full description, all images, tags, and tools used. |
| search_behance_profilesA | Search for user profiles on Behance by keyword. Returns username, display name, avatar, location, followers, appreciations, and project count. |
| get_behance_profile_detailsB | Get detailed information about a specific Behance user profile including bio, company, occupation, social links, and complete stats. |
| search_behance_imagesA | Search for images on Behance by keyword. Returns image URLs with dimensions, associated project info, and creator details. |
| get_behance_jobsA | Get job listings from Behance. Returns job title, company, location, job type, posted date, required skills, and remote availability. |
| get_behance_job_detailsA | Get detailed information about a specific Behance job listing including full description and salary info. |
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 7 tools
All tools have distinct purposes: job details vs list, profile details, project details, and separate searches for images, profiles, and projects. No overlap in functionality, so an agent can easily distinguish them.
All tool names follow a consistent 'verb_behance_noun' pattern: get_behance_*_details, get_behance_*, search_behance_*. All lowercase with underscores, no mixed conventions.
7 tools is appropriate for a read-only API covering profiles, projects, jobs, and image search. Not too few (covers main resources) nor too many (avoids bloat).
Covers search and detail retrieval for the main resource types. However, missing a direct tool to list projects by a specific user (only search by keyword). Minor gap but still functional for most use cases.